public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: info address "range"
Date: Tue, 28 Feb 2012 20:25:00 -0000	[thread overview]
Message-ID: <8362eqembm.fsf@gnu.org> (raw)
In-Reply-To: <CAN9gPaFsOEjUctLpKGtGahdd3xVG0eapsoOzJ3vbFJmYD9+zoA@mail.gmail.com>

> Date: Tue, 28 Feb 2012 15:01:37 -0500
> From: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
> Cc: gdb@sourceware.org
> 
> On Mon, Feb 27, 2012 at 10:58 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Re this:
> >
> >  (gdb) frame 2
> >  #2  0x0100ffda in compact_small_strings () at alloc.c:2271
> >  2271                abort ();
> >  (gdb) info address from
> >  Symbol "from" is multi-location:
> >    Range 0x100f452-0x100f45c: a variable in $esi
> >
> > What exactly the "range xxxx-yyyy" mean?  There's nothing in the
> > manual about this format.  Is that the range of PC values?  If so,
> > then since the current frame address is not within those limits, it
> > seems, and therefore the information is not helpful.
> >
> > Is there any way of knowing where will the variable be found for the
> > current PC value?
> 
> Most likely this means that if the current pc is outside of those
> limits, the variable is not available anywhere.

Thanks.  I will at least describe this output in the manual.

      reply	other threads:[~2012-02-28 20:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28  3:56 Eli Zaretskii
2012-02-28 20:01 ` Daniel Jacobowitz
2012-02-28 20:25   ` Eli Zaretskii [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=8362eqembm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=daniel.jacobowitz@gmail.com \
    --cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).