Producing a "program trace" using GDB and Python

This page cannot be shown here. You can still read it on the original site — the toolbar below keeps your place in the directory.

Sometimes, to understand what a program is doing, I’m tempted to add a log message at the start and end of every function, something like entering foo() and returning from foo() . When there are only a few functions this is easy enough to do manually, but if you want it for every function, some automation would be welcome. This could be automated using gcc’s -finstrument-functions ,…

Read on /post/gdb-python-trace/ ↗