On Mon, Feb 11, 2008 at 04:05:43PM +0000, Frans Pop wrote: > On Monday 11 February 2008, you wrote: > > Then, you open it using: gdb <name-of-the-program> /tmp/the.core, and > > a full backtrace should help (you will probably need to install > > python-apt-dbg) [bt full in gdb]. > > Thanks for the clear instructions! > > Got the core, but the info from gdb is, uh, disappointing: > $ gdb apt-listchanges apt-listchanges.2498.core > [bla bla] > This GDB was configured as "sparc-linux-gnu"... > "/usr/bin/apt-listchanges": not in executable format: File format not > recognized > Core was generated by `/usr/bin/python /usr/bin/apt-listchanges --apt'. > Program terminated with signal 10, Bus error. > #0 0xf7f7b078 in ?? () > (gdb) bt full > #0 0xf7f7b078 in ?? () > No symbol table info available. > > That's with python-apt-dbg installed.
try to install python-dbg as well. Though if the core is named apt-listchanges.*.core it really means that it's /usr/bin/apt-listchanges that is failing, so probably a python bug. You can reuse the core without generating a new one after having installed python-dbg. Oh and I'm *COMPLETELY* silly. it's not: gdb /usr/bin/atp-listchanges /path/to/core but, $ gdb /usr/bin/python /path/to/core. apt-listchanges is obviously not ELF like gdb complains :PP -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpRGaElprSUA.pgp
Description: PGP signature
