Ubuntu
gdb package

[apport] gdb crashed with SIGSEGV in symbol_demangled_name()

Bug #86879 reported by FinCoder on 2007-02-21

4

Affects		Status	Importance	Assigned to	Milestone
	gdb (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: gdb

no idea

ProblemType: Crash
Date: Wed Feb 21 16:14:57 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gdb
Package: gdb 6.6.dfsg-1ubuntu2
ProcCmdline: gdb -nw -n -batch -x /tmp/kde-jarkko/drkonqi1BYZjc.tmp kdeinit 6634
ProcCwd: /home/jarkko
ProcEnviron:
LANGUAGE=fi_FI:fi:en_GB:en
PATH=/home/jarkko/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=fi_FI.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: gdb
StacktraceTop:
symbol_demangled_name ()
?? ()
?? ()
?? ()
?? ()
Uname: Linux localhost 2.6.20-8-386 #2 Tue Feb 13 05:15:43 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message

FinCoder (jarkko-korpi) wrote on 2007-02-21:

#1

CoreDump.gz Edit (2.6 MiB, application/x-gzip)
Dependencies.txt Edit (154 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (954 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (621 bytes, text/plain; charset="utf-8")
Registers.txt Edit (497 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (569 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (333 bytes, text/plain; charset="utf-8")

Revision history for this message

Daniel Holbach (dholbach) wrote on 2007-02-22:

#2

debug backtrace Edit (16.1 KiB, text/plain)

Revision history for this message

Martin Pitt (pitti) wrote on 2007-02-22:

#3

Forwarded upstream: http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2234 (LP doesn't know about gnats)

Changed in gdb:
importance:	Undecided → Medium
status:	Unconfirmed → Confirmed

Revision history for this message

Martin Pitt (pitti) wrote on 2007-02-22:

#4

Can you reproduce this problem in any way? Upstream needs a reproducible test case:

"The symbol table pointer looks obviously corrupt. There's not much more I can say about this without a test case."

Did you happen to manually file a bug about the original crash in kdeinit as well?

Changed in gdb:
status:	Confirmed → Needs Info

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-07-05:

#5

Is that still happening?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2007-09-21:

#6

[Expired for gdb (Ubuntu) because there has been no activity for 60 days.]

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.