From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: naesten@gmail.com (Samuel Bronson)
Cc: thiago.bauermann@gmail.com (Thiago Jung Bauermann),
gdb@sourceware.org,
schwab@linux-m68k.org (Andreas Schwab),
Catherine.Smith@arrows.demon.co.uk (Catherine Smith)
Subject: Re: Backtracing broken core dumps
Date: Mon, 20 Jul 2009 19:53:00 -0000 [thread overview]
Message-ID: <200907201952.n6KJqlVV020759@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <87fxcrdukv.wl%naesten@gmail.com> from "Samuel Bronson" at Jul 20, 2009 03:26:40 PM
Samuel Bronson wrote:
> At Sun, 19 Jul 2009 22:49:05 -0300,
> Thiago Bauermann wrote:
> > IIRC Ulrich Weigand considers that usage of the frame command to be
> > deprecated... I don't know the rationale though.
>
> I believe the rationale is that it doesn't actually work very well :-).
Well yes, and more importantly that it cannot be made to work well,
because -as Paul Koning already pointed out- just specifying a stack
address simply does not reliably identify a stack frame. On many
platforms, you *need* a PC in addition to the stack address in order
to be able to unwind further. On some platforms (IA64) you may even
need yet more information (register stack address) ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-07-20 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 16:03 Catherine Smith
2009-07-19 16:11 ` Andreas Schwab
2009-07-20 1:47 ` Thiago Jung Bauermann
2009-07-20 19:26 ` Samuel Bronson
2009-07-20 19:53 ` Ulrich Weigand [this message]
2009-07-20 16:18 ` Paul Koning
2009-07-20 12:06 ` Daniel Jacobowitz
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=200907201952.n6KJqlVV020759@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=Catherine.Smith@arrows.demon.co.uk \
--cc=gdb@sourceware.org \
--cc=naesten@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=thiago.bauermann@gmail.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