Coroutine debugging tools
Open
- Dominant language
- C++
- Stars
- 30.5k
- Forks
- 5.9k
- PR merge metrics
- No merged PRs in 30d
Description
I've been using the coroutine functions, and can't help but notice that debugging coro code is a disaster. Pointers towards doing the following would be good:
- Looking at a coroutine backtrace with the ability to inspect each "stack frame" (inspect local variables, function arguments, etc) (gdb `bt/up/down/frame /info locals` equivalents)
- Looking at all the pending async tasks (gdb `info threads/thread ` equivalent)
The current `co_bt.py` script just shows a backtrace without the ability to inspect any of the frames.
Contributor guide
Assessment
This issue has not been assessed yet.