From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@streamline-computing.com>
Cc: gdb@sources.redhat.com
Subject: Re: Opteron Stack Woes
Date: Tue, 17 Aug 2004 14:10:00 -0000 [thread overview]
Message-ID: <20040817141014.GA9175@nevyn.them.org> (raw)
In-Reply-To: <1092750299.3127.34.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com>
On Tue, Aug 17, 2004 at 02:44:59PM +0100, David Lecomber wrote:
> Thanks Daniel,
>
> > readelf -wF is probably your best bet. But is the only problem the
> > fact that the backtrace didn't stop at _start?
>
> I've seen worse stack traces than this on the Opteron, particularly one
> that had Lustre kernel patches applied -- but I don't know if that was
> related.. I'll keep an eye out for further problems.
>
> I figured that the "Incomplete CFI data" might be an issue. I don't
> know enough about this area yet to do anything..
It's not a problem - take a look in the archive.
>
> > You might want to investigate why the backtrace didn't stop earlier, at
> > main or at a fortran entry point. GDB may be confused about
> > main_name().
>
> Attached is the readelf -wF info, can you see anything wrong with the
> 0x040d7ad entry?
No, it looks fine.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-17 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 11:46 David Lecomber
2004-08-17 13:11 ` Daniel Jacobowitz
2004-08-17 13:29 ` David Lecomber
2004-08-17 14:10 ` Daniel Jacobowitz [this message]
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=20040817141014.GA9175@nevyn.them.org \
--to=drow@false.org \
--cc=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