This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Understanding GDB frames
On Tue, May 22, 2007 at 11:32:41AM -0700, Jim Ingham wrote:
> I don't see what the bad effect of not destroying the varobj if the frame id is
> identical is. You might get an errant "value changed" notification. Other than
> that, I can't see what you would be gaining.
>
> If we're going to do some extra work to make sure we mark variables out of
> scope when their frames are exited, we should get something real out of it. So
> far it seems the benefit is only theoretical.
Sure. I'm not seriously proposing we do that extra work, though I did
think about it. But what we do need is to clarify our semantics so
that front ends know what to expect. Should varobjs be destroyed when
we leave and re-enter a function? If the answer is "maybe", then that
is confusing enough to deserve some more explanation :-)
--
Daniel Jacobowitz
CodeSourcery