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: Tue, 12 Oct 2010 20:12:00 -0000 [thread overview]
Message-ID: <20101012201145.GZ8337@caradoc.them.org> (raw)
In-Reply-To: <201010121656.o9CGuMDo025020@d12av02.megacenter.de.ibm.com>
On Tue, Oct 12, 2010 at 06:56:22PM +0200, Ulrich Weigand wrote:
> Hmm, I noticed one set of problems is due to the __libc_do_syscall
> function you added in this patch:
>
> http://sourceware.org/ml/gdb-patches/2010-10/msg00137.html
Wrong link :-)
> The GDB prologue parser would actually be easily capable of understanding
> this function prologue. However, it doesn't work because GDB does not even
> find the start of the function in the first place, since the symbol is
> present only in the regular symbol table (which is stripped), and not in
> the dynamic symbol table, because of the ".hidden" directive.
>
> Is there any particular reason why this function could not be at least
> .protected instead?
It doesn't need to be exposed; that would waste space in the dynamic
symbol table. Plus I don't understand the complete details, but
.protected is problematic.
I am not real sympathetic. Either have unwind info, or if you have a
system where that is not practical, implement .ARM.exidx based
unwinding for GDB. It can't be done in general but it can be done for
the standard table formats; there's code in readelf to dump them, for
instance.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-10-12 20:12 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
2010-10-12 16:56 ` Ulrich Weigand
2010-10-12 20:12 ` Daniel Jacobowitz [this message]
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=20101012201145.GZ8337@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