GDB module to activate frames

[vinipsmaker]

Folly's fibers (based on Boost.Context) have a GDB script to debug fibers. The script only has a few helpers to list fibers and inspect a fiber.

Once we find a valid pointer to a boost::context::fiber in the debugging session, it'd be useful to have two simple GDB commands to inspect its call stack. The lines related to this feature in the Facebook script are: https://github.com/facebook/folly/blob/85465c8ef64be895bd15a0a315f3698fb5dc685f/folly/fibers/scripts/gdb.py#L191-L247 (supporting documentation)

[olk]

I'm not familiar with GDB scipts...
you are welcome to provide a patch that supports GDB scripts

[vinipsmaker]

[patches welcome]

Good. Would x86-only support be okay for the scripts?

[lenerd]

Hi,

for debugging of some code using Boost.Fiber, I wrote some custom GDB commands for e.g. finding the scheduler object, listing the running worker fibers and their backtraces, as well as switching the context to a fiber.

The code is available at here, but so far it has not been documented nor tested much (besides my own debugging sessions). Feel free to take a look. So far it requires Boost compiled in debug mode and is specific to x86-64.