From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, roland@redhat.com
Subject: Re: [rfc] Decode "is a variable with complex or multiple locations" (PR 8399)
Date: Mon, 21 Sep 2009 03:20:00 -0000 [thread overview]
Message-ID: <83iqfdugsk.fsf@gnu.org> (raw)
In-Reply-To: <20090920205109.GA24360@host0.dyn.jankratochvil.net>
> Date: Sun, 20 Sep 2009 22:51:09 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Roland McGrath <roland@redhat.com>
>
> the attached patch now prints:
>
> (gdb) info address val
> Symbol "val" is a variable with multiple locations, for PC inclusive - exclusive:
> 0x5157c9 - 0x5157e9: stored relative to frame base at offset -20
> 0x5157e9 - 0x5157f2: stored relative to register rsp at offset 60
> 0x5157f2 - 0x515835: stored relative to frame base at offset -20
> and optimized out in ranges not covered above.
This is a very useful feature, thanks.
> (a) While it does what `info address' should do I think you (+me) wished more
> just the single line valid for the current PC.
>
> This would do `info scope *$pc' but that one prints _all_ the visible
> variables with no way how to request just one variable.
We could have "info scope *$pc VAR" that does it for a single
variable.
> As the attached patch mostly just reimplements already available readelf
Does it mean this patch will only work with ELF-based executables, not
with any executable that uses DWARF-2?
> one should probably change `info address' to print it only for the current
> PC address.
Yes, I agree.
next prev parent reply other threads:[~2009-09-21 3:20 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 [this message]
2009-09-21 3:48 ` Roland McGrath
2009-09-25 21:53 ` Tom Tromey
2009-09-25 22:07 ` 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=83iqfdugsk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=roland@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