This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
bt shows only one frame
- From: Baurjan Ismagulov <ibr at ata dot cs dot hun dot edu dot tr>
- To: gdb at sources dot redhat dot com
- Date: Tue, 2 Dec 2003 21:13:41 +0200
- Subject: bt shows only one frame
Hello,
I'm trying to debug a core file with gdb 5.3 on AMD64 platform. I expect
to see the call stack until either main or a signal handler, but bt
command shows only one line. Is this intended behaviour, is my stack
corrupt, or is it a known issue with gdb on this platform?
I would greatly appreciate any help. I couldn't find anything in the
archives or using Google.
Thanks in advance,
Baurjan.
(gdb) linuxclient:/usr/ibr/tmp/rpm/BUILD/showconsole-1.01 # gdb /sbin/blogd /core
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...
Core was generated by `/sbin/blogd /dev/ttyS0'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib64/libutil.so.1...done.
Loaded symbols for /lib64/libutil.so.1
Reading symbols from /lib64/libc.so.6...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
#0 0x0000002a957dadf4 in fileno_unlocked () from /lib64/libc.so.6
(gdb) bt
#0 0x0000002a957dadf4 in fileno_unlocked () from /lib64/libc.so.6
(gdb) up
Initial frame selected; you cannot go up.