This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Opteron Stack Woes
- From: David Lecomber <david at streamline-computing dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 17 Aug 2004 13:01:51 +0100
- Subject: Opteron Stack Woes
Chaps,
What's the best way to get enough info to you to help fix some ropey
stacks that we're seeing on Opteron (SuSE 9), even with the latest CVS?
Typically we see things like
(gdb) n
During symbol reading, Incomplete CFI data; unspecified registers at
0x000000000040d7ad.
and a stacktrace of thousands (and more?) lines
#0 main__ () at trees.f90:912
#1 0x00000000004188b8 in __f90_main ()
#2 0x0000000000418890 in main ()
#3 0x0000002a95dbbc9e in __libc_start_main () from /lib64/libc.so.6
#4 0x0000000000400f2a in _start () at ../sysdeps/x86_64/elf/start.S:96
#5 0x0000007fbffff2a8 in ?? ()
#6 0x0000000000000000 in ?? ()
#7 0x0000000000000001 in ?? ()
#8 0x0000007fbffff5b2 in ?? ()
#9 0x0000000000000000 in ?? ()
#10 0x0000007fbffff5f7 in ?? ()
#11 0x0000007fbffff610 in ?? ()
#12 0x0000007fbffff654 in ?? ()
#13 0x0000007fbffff686 in ?? ()
#14 0x0000007fbffff696 in ?? ()
#15 0x0000007fbffff6a7 in ?? ()
#16 0x0000007fbffff6ce in ?? ()
#17 0x0000007fbffff6de in ?? ()
etc...
Would a readelf -w output assist? I don't think I can reproduce the
error with any of the GNU compilers.
Cheers
David