From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI: -var-update bug
Date: Fri, 08 Dec 2006 20:09:00 -0000 [thread overview]
Message-ID: <17785.50551.255052.307043@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061208200434.GA25405@nevyn.them.org>
> Randomisation isn't even the issue - I think that what you've got now
> is simply an accident, and varobjs associated with a particular frame
> should not become valid if a similar looking frame reappears later.
OK that shows I've misunderstood. I thought it was looking for a frame
to associate with it.
> Right now we never delete varobjs automatically. We could preserve
> that, but set a flag on the varobjs indicating they're permanently out
> of scope?
What value is a variable object that is permanently out of scope?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-12-08 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 19:38 Nick Roberts
2006-12-08 19:43 ` Daniel Jacobowitz
2006-12-08 19:56 ` Nick Roberts
2006-12-08 20:04 ` Daniel Jacobowitz
2006-12-08 20:09 ` Nick Roberts [this message]
2006-12-08 20:23 ` Daniel Jacobowitz
2006-12-09 20:47 ` Nick Roberts
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=17785.50551.255052.307043@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.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