This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI: "freezing" variable object
- From: Daniel Jacobowitz <drow at false dot org>
- To: Vladimir Prus <ghost at cs dot msu dot su>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 4 May 2006 11:15:42 -0400
- Subject: Re: MI: "freezing" variable object
- References: <e2agjf$kvs$1@sea.gmane.org>
On Fri, Apr 21, 2006 at 03:44:47PM +0400, Vladimir Prus wrote:
>
> Hi,
> what's the best way to "freeze" a variable object, so that it's current
> value is saved, and is not changed on any -var-update invocation?
>
> I need this in order to implement a functionality where user can remember
> the current value of an expression for future reference. I'd expect the
> user to still be able to open composite object (using -var-list-children),
> so saving just textual representation I not enough.
>
> I can get the desired effect with:
>
> print expression
> -var-create $NNN
>
> where $NNN is the history item, but am I supposed to use CLI command for
> that?
I've got no idea, sorry. It does seem like (A) this would be a nice
functionality to have, and (B) the general relationship between varobjs
and the expressions which created them is not sufficiently documented.
--
Daniel Jacobowitz
CodeSourcery