This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2056: gdb produces endless backtraces on AMD64
- From: devvv at devvv dot de
- To: gdb-gnats at sources dot redhat dot com
- Cc: richard at hirner dot at
- Date: 20 Dec 2005 17:48:19 -0000
- Subject: gdb/2056: gdb produces endless backtraces on AMD64
- Reply-to: devvv at devvv dot de
>Number: 2056
>Category: gdb
>Synopsis: gdb produces endless backtraces on AMD64
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Dec 20 17:58:01 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: devvv@devvv.de
>Release: gdb-6.3 debian
>Organization:
>Environment:
Ubuntu 5.10, AMD64
>Description:
Calling gdb on a segfaulted process and doing "bt", "thread apply all bt full" produces and endless backtrace. After the normal back trace, lines as these:
"No symbol table info available.
#208 0x0000000000000000 in ?? ()
No symbol table info available.
#209 0x0000000000000000 in ?? ()"
appear infinite times and gdb doesn't get finished. I think this bug is related to the AMD64 platform.
See also:
http://bugzilla.gnome.org/show_bug.cgi?id=321296
http://bugzilla.gnome.org/show_bug.cgi?id=316859
>How-To-Repeat:
1) Let a third-party executable crash (not too difficult with Nautilus or Totem)
2) Start gdb with the core file and a command file which contains "bt", "thread apply all bt full" and "q" and pipe the output into a file:
/usr/bin/gdb --batch --quiet --command=/usr/share/bug-buddy/gdb-cmd /usr/bin/totem core.2938 | tee bt
3) After printing the correct part of the backtrace, gdb will never finish and reproduce always the same line (see above)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: