From: Pedro Alves <palves@redhat.com>
To: Will Newton <will.newton@linaro.org>
Cc: gdb-patches@sourceware.org, patches@linaro.org
Subject: Re: [PATCH 1/3] gdb/printcmd.c: Fix printing of Thumb minimal symbols.
Date: Wed, 05 Jun 2013 15:21:00 -0000 [thread overview]
Message-ID: <51AF576C.7070302@redhat.com> (raw)
In-Reply-To: <51AF1444.5080800@linaro.org>
On 06/05/2013 11:34 AM, Will Newton wrote:
>
> In build_address_symbolic we call gdbarch_addr_bits_remove for
> symbols in the symbol table but not for minimal symbols. This
> causes a failure in gdb.cp/virtfunc.exp on ARM, as the address
> of the virtual thunk is given an offset of 1 when in Thumb mode.
>
> gdb/ChangeLog:
>
> 2013-06-05 Will Newton <will.newton@linaro.org>
>
> * printcmd.c (build_address_symbolic): Call
> gdbarch_addr_bits_remove for text minimal symbols.
> ---
> gdb/printcmd.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/gdb/printcmd.c b/gdb/printcmd.c
> index 7beb334..619e684 100644
> --- a/gdb/printcmd.c
> +++ b/gdb/printcmd.c
> @@ -689,6 +689,16 @@ build_address_symbolic (struct gdbarch *gdbarch,
> {
> if (SYMBOL_VALUE_ADDRESS (msymbol) > name_location || symbol == NULL)
> {
> + /* If this is a function (i.e. a code address), strip out any
> + non-address bits. For instance, display a pointer to the
> + first instruction of a Thumb function as <function>; the
> + second instruction will be <function+2>, even though the
> + pointer is <function+3>. This matches the ISA behavior. */
> + if (MSYMBOL_TYPE (msymbol) == mst_text
> + || MSYMBOL_TYPE (msymbol) == mst_text_gnu_ifunc
> + || MSYMBOL_TYPE (msymbol) == mst_file_text)
> + addr = gdbarch_addr_bits_remove (gdbarch, addr);
Shouldn't we do this for all text symbols, and thus for
mst_solib_trampoline too?
Not sure whether the if above that seems to be checking for
text symbols is missing it too:
if (msymbol != NULL
&& MSYMBOL_HAS_SIZE (msymbol)
&& MSYMBOL_SIZE (msymbol) == 0
&& MSYMBOL_TYPE (msymbol) != mst_text
&& MSYMBOL_TYPE (msymbol) != mst_text_gnu_ifunc
&& MSYMBOL_TYPE (msymbol) != mst_file_text)
msymbol = NULL;
(I wish this bit had a comment mentioning what's it about.)
> +
> /* The msymbol is closer to the address than the symbol;
> use the msymbol instead. */
> symbol = 0;
--
Pedro Alves
next prev parent reply other threads:[~2013-06-05 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 10:34 Will Newton
2013-06-05 15:21 ` Pedro Alves [this message]
2013-06-05 15:27 ` Will Newton
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=51AF576C.7070302@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patches@linaro.org \
--cc=will.newton@linaro.org \
/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