You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using GDB and OpenOCD from the command line, info threads shows me thread names as well as thread ids.
When using VSCode, the Callstack window only shows thread ids, and I have to oepn them and browse the callstacks to select the correct thread.
Describe the solution you'd like
Would be nice to see the provided thread names :)
Describe alternatives you've considered
living with it? :)
Additional context
VS Code extension version 1.9.0 plus the fix in #1413)
Screenshot of VSCode:
Vs screenshot from console GDB. Same openocd behind the scenes: v0.12.0-esp32-20230921
Vs screenshot from a non-esp32 embedded freertos project in vscode:
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Feature Request]: RTOS thread view to show thread names
[Feature Request]: RTOS thread view to show thread names (VSC-1579)
Jan 29, 2025
Is your feature request related to a problem? Please describe.
When using GDB and OpenOCD from the command line,
info threads
shows me thread names as well as thread ids.When using VSCode, the Callstack window only shows thread ids, and I have to oepn them and browse the callstacks to select the correct thread.
Describe the solution you'd like
Would be nice to see the provided thread names :)
Describe alternatives you've considered
living with it? :)
Additional context
VS Code extension version 1.9.0 plus the fix in #1413)
Screenshot of VSCode:
Vs screenshot from console GDB. Same openocd behind the scenes: v0.12.0-esp32-20230921
Vs screenshot from a non-esp32 embedded freertos project in vscode:
The text was updated successfully, but these errors were encountered: