This is the mail archive of the
mailing list for the GDB project.
Re: MI floating varobj of invalid value
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb at sourceware dot org
- Date: Sun, 27 Apr 2008 06:06:29 +0300
- Subject: Re: MI floating varobj of invalid value
- References: <email@example.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Vladimir Prus <firstname.lastname@example.org>
> Date: Sun, 27 Apr 2008 01:27:48 +0400
> However, if frontend tries to create varobj for foo
> at the first stop, and 'foo' is not in scope, then varobj will not be created.
Why is that? Since a floating varobj's expression is re-parsed every
time, you should be able to delay parsing and not fail creation
because some of its terms are not in scope, right?
> Does making creation of floating varobj always succeed seem a good idea?
Yes, I think so.