From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, Roland McGrath <roland@redhat.com>
Subject: Re: [rfc] Decode "is a variable with complex or multiple locations" (PR 8399)
Date: Fri, 25 Sep 2009 22:07:00 -0000 [thread overview]
Message-ID: <20090925220716.GA3380@caradoc.them.org> (raw)
In-Reply-To: <m31vluvghu.fsf@fleche.redhat.com>
On Fri, Sep 25, 2009 at 03:53:01PM -0600, Tom Tromey wrote:
> Jan> (c) "a variable in register rsi" vs. "DW_OP_reg4":
>
> Jan> (c1) Extending the readelf<->gdb shared code to print register
> Jan> names (4->rsi) may not be acceptable for arch-independent readelf.
>
> We can add a callback that GDB would use to supply the register name.
I've always wanted readelf to print these names, anyway.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-09-25 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090916201132.366872766@magilla.sf.frob.com>
2009-09-20 20:51 ` Jan Kratochvil
2009-09-21 3:20 ` Eli Zaretskii
2009-09-21 3:48 ` Roland McGrath
2009-09-25 21:53 ` Tom Tromey
2009-09-25 22:07 ` Daniel Jacobowitz [this message]
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=20090925220716.GA3380@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=roland@redhat.com \
--cc=tromey@redhat.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