Make Thread viewer graphical with timelines

RE: Make Thread viewer graphical with timelines

Edvin — Fri, 07 Mar 2025 14:33:23 GMT

Will do 🙂

Best regards,

Edvin

RE: Make Thread viewer graphical with timelines

d2sc — Thu, 06 Mar 2025 20:45:16 GMT

Hi Edvin, Can you request the ability to periodically read variables from the cpu in the debugger without hitting a breakpoint/ pausing the cpu? Segger Embedded Studio Supports this.

RE: Make Thread viewer graphical with timelines

Edvin — Thu, 27 Feb 2025 07:36:51 GMT

Thank you,

I will forward this to our VS Code extension team.

Best regards,

Edvin

RE: Make Thread viewer graphical with timelines

devangs33 — Tue, 25 Feb 2025 17:13:14 GMT

Thanks for getting back, I would imagine this the same way any debugger works. So yes, when you step through the code, you should see which thread took the execution time using a bar, as well as acquired a certain mutex. Or if the code were free-running and someone were to pause it, just show the last thread that was being run & mutex that was acquired. Same for semaphores, but just showing count change works for that.

RE: Make Thread viewer graphical with timelines

Edvin — Tue, 18 Feb 2025 07:37:16 GMT

The team replied that it would be an interesting feature. However, we have one limitation. When the application is running, the debugger can't communicate with the target. This means it can't know what happened before it pauses, and in this case, it can only know the current state of the threads. They said:

"It would be nice to know how the user imagined this feature given this fact. Should we build a timeline while 'stepping'? How would it work while 'run'+'pause'+'run'+'pause' cycle when we can't know anything during running?"

I do understand if this is something you haven't considered, but seeing as you are involved in this training situation, we would appreciate it if you have any input/suggestions.

Best regards,

Edvin

RE: Make Thread viewer graphical with timelines

Edvin — Mon, 17 Feb 2025 13:09:13 GMT

Hello,

Thank your for the suggestion! I will forward this to our VS Code team as a feature request.

Best regards,

Edvin