Plumbing Life's Depths - Want that tool, but cores are useless without debug symbols

Tried to get the gdb-with-python recipe (that we discussed at PyGTA) to investigate the crashes from the rewrite. I gather it requires that you have debugging symbols built for Python and all of the modules for it (well, to be able to trace into them, anyway). I'm on an Ubuntu box here, not really sure how to create the debugging symbols without needing to rebuild from source. I'm guessing that there's something like Gentoo's "splitdebug" available in some package if I knew where to look.

I've got my machine at home (Gentoo) rebuilding Python, pygame, wxPython, numpy, etceteras with debugging symbols (turns out Gentoo auto-strips (duh!) even though I have -g specified in the make options, so no debug symbols there at the moment). I want to eventually get the pyglet-generator-based branch fixed up, and that will require the debugging symbols when I get around to it.

Not much else done today other than to get all of the Demos/tests in PyOpenGL, OpenGLContext and PyOpenGL-Demo working under Ubuntu Hardy. Wanted to do Win32 as well, but ran out of time. Especially need to check/fix extensions as we have a bug reported for them.

Comments

Heikki Toivonen on 09/05/2008 5:52 p.m. #

Have you tried installing *-dbg packages, like python2.5-dbg?
Marius Gedminas on 09/05/2008 9:58 p.m. #

https://wiki.ubuntu.com/DebuggingProgramCrash tells you how to download debug symbols for all Ubuntu packages.
khaled on 09/05/2008 11:02 p.m. #

may be all what you is need python*-dbg packages
Jean-Paul on 09/06/2008 7:36 a.m. #

A lot of Debian packages have a "-dbg" version. The primary difference between the normal packages and these is generally that these include debugging symbols. You don't even have to be running python-dbg when your core is generated. You can install python-dbg after you already have a core and gdb will be able to find the symbols it needs. A lot of extensions packages also have -dbg versions, and it looks like Hardy has a *much* more complete set than previous releases did, though I'm not sure if it's 100%.
Daniel Drake on 09/06/2008 10:06 p.m. #

In Gentoo you can do: FEATURES=nostrip emerge <foo>
Mike Fletcher on 09/07/2008 2:24 a.m. #

I actually went with the splitdebug rather than nostrip option for Gentoo. I also had to do an ebuild ... unpack in order to get the source so that it was easy to browse the crash-point-code. However, I wasn't able to get the gdb python extensions to work in that environment.
Mike Fletcher on 09/07/2008 2:27 a.m. #

Thanks all for the Ubuntu notes, I'll try the dbg packages when I'm working on that machine again.