Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: "Srinath Avadhanula" <srinathava@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Variables created with -var-create going out of scope unexpectedly?
Date: Thu, 20 Nov 2008 15:37:00 -0000	[thread overview]
Message-ID: <200811201836.10961.vladimir@codesourcery.com> (raw)
In-Reply-To: <ed97310c0811200632x4f68e34eubc2707e32889773b@mail.gmail.com>

On Thursday 20 November 2008 17:32:21 Srinath Avadhanula wrote:
> Hi Volodya,
> 
> On Thu, Nov 20, 2008 at 8:59 AM, Vladimir Prus
> <vladimir@codesourcery.com> wrote:
> >> first time the breakpoint is hit and then do "-var-update 1 *" each
> >> subsequent time the break-point is hit, I only see 'in_scope="true"'
> >> the two times when foo() is reached with exactly the same stack. Is
> >> this expected? Is there an equivalent of gdb's "display" command for
> >> GDB/MI?
> >
> > GDB/MI documentation in CVS HEAD describes this.
> >
> 
> Thanks for the info! Sorry for my ignorance, but I cannot seem to
> figure out how to get the CVS HEAD of the GDB/MI documentation. Could
> you please point me to it? I tried downloading a few things from the
> GDB web-site, but couldn't figure out the latest version...
> 
> Also, if
> 
> http://sourceware.org/gdb/onlinedocs/gdb_25.html#SEC413
> 
> is the latest version, it doesn't seem to make any special mention of
> -var-create with respect to going out of scope...

In general, you can get CVS HEAD sources using instructions at:

	http://www.gnu.org/software/gdb/current/

But I've just realized the patch is not actually checked in yet. Please see:

	http://permalink.gmane.org/gmane.comp.gdb.patches/44757

for a doc patch -- search for "floating" varobjs.

- Volodya


      reply	other threads:[~2008-11-20 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 13:47 Srinath Avadhanula
2008-11-20 14:00 ` Vladimir Prus
2008-11-20 14:33   ` Srinath Avadhanula
2008-11-20 15:37     ` Vladimir Prus [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=200811201836.10961.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb@sources.redhat.com \
    --cc=srinathava@gmail.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