Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: gdb@sources.redhat.com
Subject: Opteron Stack Woes
Date: Tue, 17 Aug 2004 11:46:00 -0000	[thread overview]
Message-ID: <1092744111.3127.25.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> (raw)

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


             reply	other threads:[~2004-08-17 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 11:46 David Lecomber [this message]
2004-08-17 13:11 ` Daniel Jacobowitz
2004-08-17 13:29   ` David Lecomber
2004-08-17 14:10     ` Daniel Jacobowitz
2004-08-17 13:48   ` Michael Chastain
2004-08-17 14:47 ` H. J. Lu
2004-08-25 19:49 ` [RFC] Backtrace limit David Lecomber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1092744111.3127.25.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com \
    --to=david@streamline-computing.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox