From: "Stefan Burström" <f94sbu@efd.lth.se>
To: gdb@sources.redhat.com
Subject: Re: rs6000 / ppc backend in gdb
Date: Mon, 01 Aug 2005 20:45:00 -0000 [thread overview]
Message-ID: <33e255d0bad.2dcea4ea@mail.m.bonet.se> (raw)
In-Reply-To: <20050801131203.GA4405@nevyn.them.org>
Hello Daniel
On 2005-08-01, you wrote:
> On Sun, Jul 31, 2005 at 11:02:36PM +0100, Stefan Burström wrote:
>
> No, absolutely they aren't! We've learned, over years of debugging
> people's real code, that trusting the architecture defined stack layout
Well, if you don't have any debugging info available then?
> is not a good choice. For instance, on x86 -fomit-frame-pointer is
> popular to free up an additional register.
Well, I see a lot of problems on architectures where you cannot determine
the layout of the stackframe. But on those architectures you are completely
screwed anyway without debug info
> You weren't very specific about what versions you were testing, but on
> x86 you've probably got DWARF2 CFI available, which allows reliable
Well, the problem is not when debug info is available. The problem is if the
stack chain goes through the OS where no debug info at all is available.
I suppose I am pretty much on my own if I want to get this functionality
into GDB?
One interesting thing about all this is that even if the PPC backend tries
to be really nice and look at the prologue to determine various aspects of
the frame, it still assumes that the previous sp is saved where the current
sp points.
regards,
Stefan Burstrom
next prev parent reply other threads:[~2005-08-01 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 0:50 PPC stack trace Stefan Burström
2005-07-31 0:19 ` rs6000 / ppc backend in gdb Stefan Burström
2005-07-31 1:17 ` Daniel Jacobowitz
2005-07-31 22:15 ` Stefan Burström
2005-08-01 13:12 ` Daniel Jacobowitz
2005-08-01 20:45 ` Stefan Burström [this message]
2005-08-01 20:51 ` Daniel Jacobowitz
2005-08-01 21:08 ` Stefan Burström
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=33e255d0bad.2dcea4ea@mail.m.bonet.se \
--to=f94sbu@efd.lth.se \
--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