Re: Variable objects laziness

[Daniel Jacobowitz <drow@false.org>]

On Wed, Nov 29, 2006 at 03:04:10PM +1300, Nick Roberts wrote:
> Also -var-update only reports a change when the address changes and not the
> value.  Variable objects were broken before but in a different way (-var-assign
> worked but -var-update always reported that the reference value had changed).

Just so we're all on the same page, could you post a compilable test
case?  I don't need a dejagnu-ified one, just some C++.

> I think a further call to coerce_array is needed and the output to -var-update
> should look like:
> 
> 
> -var-update --all-values var1
> ^done,changelist=[{name="var1",value="4",in_scope="true",type_chan ged="false"}]
> 
> i.e the address shouldn't appear in the value field.

Is that what it did before?  I guess it's not surprising.

-- 
Daniel Jacobowitz
CodeSourcery