Comments on: Gdb is dead. Long live Gdb!

By: Tom Tromey

Tom Tromey — Tue, 25 Nov 2008 00:51:52 +0000

Yeah, python-gdb will auto-load python based on the “objfiles” that are opened. For an objfile X, gdb will look for “X-gdb.py”; if it exists, it will be loaded.

So, in this case, X might be /usr/bin/nautilus. The lookup process also handles separate debug info; so you can stick the python there if you prefer.

We’ve talked about stuffing this into the debug info but I am not sure if we will. I do think I’ll expand the file search so we don’t clutter /usr/bin and /usr/lib.

Once the API is a bit more stable I expect we’ll try to get a few projects to ship their debug hacks. I plan to ship at least one (libstdc++ pretty-printers) in F11.

By: johan

johan — Wed, 19 Nov 2008 17:14:44 +0000

Neat idea, I’ve wanted to do this for some time.

Maybe the g_signal_emit frame can be removed as well, since it doesn’t give a lot of extra information.

Next step, integrate this with language bindings, so we can go from say JS -> C back and forth and still make sense of the tracebacks.

By: Ian McKellar

Ian McKellar — Tue, 18 Nov 2008 19:16:19 +0000

Wow. That’s the best thing I’ve seen in a long time. Almost enough to make up for automake, eh?

Ian

By: alexl

alexl — Tue, 18 Nov 2008 18:09:52 +0000

colin: I think that might be possible with the python stuff. It has some autoload per object file feature.

By: Colin Walters

Colin Walters — Tue, 18 Nov 2008 18:05:40 +0000

My random idea on this was to be able to attach gdb scripts inside the .debuginfo packages. So the projects themselves maintain them, and you don’t have to go hunting on the intertubes to find them.

By: Abderrahim

Abderrahim — Tue, 18 Nov 2008 13:28:56 +0000

Looks great, I hope I’ll find some time to integrate this with my vala patch