Binary package hint: gdb
On Lucid upgraded from Karmic crash when apport reporting occured
ProblemType: Crash
Architecture: amd64
Date: Tue Mar 23 07:17:50 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gdb
NonfreeKernelModules: nvidia
Package: gdb 7.1-1ubuntu1
ProcCmdline: gdb --batch --ex file\ /usr/bin/python2.6 --ex core-file\ /tmp/tmpzRDdSI --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ (char*)\ __abort_msg
ProcEnviron:
LANG=cs_CZ.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: gdb
Title: gdb crashed with RuntimeError in __repr__()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
This bug was fixed in the package python2.6 - 2.6.5-1ubuntu4
---------------
python2.6 (2.6.5-1ubuntu4) lucid; urgency=low
* debian/
trunk. Upload for beta2 to avoid apport errors.
- Handle PyFrameObject's: LP: #543624, #548723.
- Detect cycles in object reference graph and add extra
protection: LP: #544823, LP: #552356.
-- Matthias Klose <email address hidden> Thu, 01 Apr 2010 22:53:06 +0200