From: Daniel Jacobowitz <dan@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: matthew.gretton-dann@arm.com, rearnsha@arm.com,
gdb-patches@sourceware.org
Subject: Re: [rfa] ARM prologue parsing support for Thumb-2 instructions
Date: Fri, 08 Oct 2010 13:28:00 -0000 [thread overview]
Message-ID: <20101008132747.GO23776@caradoc.them.org> (raw)
In-Reply-To: <201010081254.o98CsxQj011545@d12av02.megacenter.de.ibm.com>
On Fri, Oct 08, 2010 at 02:54:59PM +0200, Ulrich Weigand wrote:
> I've finally gotten around to finish my implementation of this.
Thanks for doing this!
> All these are caused by failures to parse the prologues of hand-written
> *ARM* assembler routines in glibc (system call handlers like nanosleep).
> These simply deviate too far from the usual rules (e.g. by intermixing
> stack saving/restoring of registers with conditional branches, or by
> temporarily saving registers into other registers instead of the stack)
> for the ARM prologue parser to be able to handle them.
>
> It seems to me that there is not much sense in attempting to support
> even this type of code. I guess we should strongly recommend to have
> (at least) glibc debuginfo files installed if you want to debug.
I agree with your conclusion. It's just not worthwhile; either
install debuginfo files, or leave .debug_frame in the stripped
libraries.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-10-08 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100719141029.GI6088@caradoc.them.org>
2010-10-08 12:55 ` Ulrich Weigand
2010-10-08 13:17 ` Richard Earnshaw
2010-10-08 13:32 ` Ulrich Weigand
2010-10-08 13:28 ` Daniel Jacobowitz [this message]
2010-10-12 16:56 ` Ulrich Weigand
2010-10-12 20:12 ` Daniel Jacobowitz
2010-10-14 14:10 ` Ulrich Weigand
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=20101008132747.GO23776@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=matthew.gretton-dann@arm.com \
--cc=rearnsha@arm.com \
--cc=uweigand@de.ibm.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