From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: matthew.gretton-dann@arm.com (Matthew Gretton-Dann)
Cc: gdb-patches@sourceware.org, rearnsha@arm.com, dan@codesourcery.com
Subject: Re: [rfc/rfa] Use ARM exception tables as GDB unwinder
Date: Thu, 21 Oct 2010 15:39:00 -0000 [thread overview]
Message-ID: <201010211538.o9LFcwo1018357@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <1287573257.3073.26.camel@e102319-lin.cambridge.arm.com> from "Matthew Gretton-Dann" at Oct 20, 2010 12:14:17 PM
Matthew Gretton-Dann wrote:
> Firstly an apology - I'm not going to be able to look at this in detail
> for a while, and Richard Earnshaw is away as well for a couple of weeks.
No problem, thanks for looking at this patch!
> One of the 'optimisations' that can be applied to the exception unwind
> table is that if two contiguous functions have the same unwind tables
> they can be merged.
[snip]
> Can the change you detail above handle this?
That depends on whether there is symbol information for those functions.
If there *is* a symbol for the second function, my patch would detect
that the symbol is closer than the unwind start address, in which case
it would refuse to use unwind data, and fall back to prologue parsing.
If there is no symbol, the patch would use the function start address
from the unwind information as part of the frame ID, which isn't really
correct. On the other hand, since there is no symbol, we don't *know*
the real start address either ... Using the address from unwind data
seems as good as anything else that we could possibly do here.
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:[~2010-10-21 15:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 0:01 Ulrich Weigand
2010-10-20 11:14 ` Matthew Gretton-Dann
2010-10-21 15:39 ` Ulrich Weigand [this message]
2010-10-20 13:27 ` Daniel Jacobowitz
2010-10-21 15:51 ` Ulrich Weigand
2010-10-21 16:02 ` Daniel Jacobowitz
2010-10-21 18:26 ` Ulrich Weigand
2010-10-21 18:42 ` Daniel Jacobowitz
2010-10-21 20:29 ` Ulrich Weigand
2010-10-21 20:43 ` Daniel Jacobowitz
2010-12-01 16:45 ` Ulrich Weigand
2010-12-12 4:21 ` Daniel Jacobowitz
2010-12-12 12:24 ` Andreas Schwab
2011-03-09 19:11 ` Ulrich Weigand
2011-03-11 22:35 ` Daniel Jacobowitz
2011-03-19 4:25 ` Ulrich Weigand
2011-03-21 14:51 ` Daniel Jacobowitz
2011-03-21 20:06 ` Ulrich Weigand
2010-10-21 22:26 ` Ulrich Weigand
2010-10-26 13:43 ` 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=201010211538.o9LFcwo1018357@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=matthew.gretton-dann@arm.com \
--cc=rearnsha@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).