folly icon indicating copy to clipboard operation
folly copied to clipboard

Coroutine debugging tools

Open IsaacKhor opened this issue 4 months ago • 0 comments

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 <x>/info locals equivalents)
  • Looking at all the pending async tasks (gdb info threads/thread <x> equivalent)

The current co_bt.py script just shows a backtrace without the ability to inspect any of the frames.

IsaacKhor avatar Oct 10 '24 20:10 IsaacKhor