So I have to click through all the callstacks of each thread in order to find out what's happening. With 20 threads, this becomes a huge chore. Can we postfix the test_trajectory headers with extra information like the callstack's current function? Similar to what your counterparts do in Visual Studio 2019
Describe the bug
OS and Version: Linux
VS Code Version: 1.43.0
C/C++ Extension Version: 0.26.3
Other extensions you installed (and if the issue persists after disabling them):
A clear and concise description of what the bug is.
To Reproduce
Run gdb with a program that uses several threads, and set a breakpoint. Then look at the callstack window.
I'm surprised today 2022 still not having this, why? GDB via DEBUG CONSOLE is not a directly choice while debugging, since we have a "CALL STACK" view here. I'm missing VS.
Type: Debugger
So I have to click through all the callstacks of each thread in order to find out what's happening. With 20 threads, this becomes a huge chore. Can we postfix the test_trajectory headers with extra information like the callstack's current function? Similar to what your counterparts do in Visual Studio 2019
Describe the bug
To Reproduce Run gdb with a program that uses several threads, and set a breakpoint. Then look at the callstack window.