gdb dies collecting informations for crash reports

Bug #318989 reported by AlbertH on 2009-01-19
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)

Bug Description

Binary package hint: gdb

kubuntu 9.04 Alpha3
gdb dies unexpectedly collecting informations for crash reports. I experienced that behavior after a kernel oop and a kttsd crash.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gdb
Package: gdb 6.8-3ubuntu2
ProcCmdline: gdb --batch --ex file\ /usr/bin/kttsmgr --ex core-file\ /tmp/tmpm570CX --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
Signal: 11
SourcePackage: gdb
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

AlbertH (alberthilbert) wrote :

StacktraceTop:printf_unfiltered (
disable_display (num=168755744)
disable_current_display ()
throw_exception (exception=
throw_it (reason=0, error=GDB_NO_ERROR,

Changed in gdb:
importance: Undecided → Medium
Connor Imes (ckimes) on 2009-01-22
Changed in gdb:
status: New → Triaged
Matthias Klose (doko) wrote :

closing this issue; please recheck with gdb in 14.04 LTS and 14.10. Feel free to re-open the issue if the problem persists.

Changed in gdb (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers