Re: Variable errors

[Keith Seitz <keiths@cygnus.com>]

On Wed, 11 Apr 2001, Fernando Nasser wrote:

> No, it is correct.  It may require some extra comment, as I can conclude
> from your message ;-)

Note that I said "not _quite_ correct", not entirely correct.

> That is intentional.  It is another variable, with the same name but
> nevertheless another one.  The blue thing is for when the _value_ of a
> variable changes.

I can buy that. My bad.

> > +            if {[lindex $UpdatedList 0] == $var} {
> > +              debug "Type changed."
> > 
> > This means that ANY root variable whose value changes is going to have
> > its offspring deleted and the variable (if it has any displayed children)
> > will also be collapsed. So if I change the value of a struct* which I was
> > viewing, all the children go away.
> > 
> 
> Nope.  The only root variable that will ever show up in there is a new
> incarnation of a type_changed varobj -- which will have the same name.

Try this:

int
main (int argc, char *argv[])
{
  int i;

  i++;
  i++;
  i++;
  exit (0);
}

As you step over the "i++;" in Insight, the value of i changes but the 
variable is never highlighted. 

Let's say that the variable "i" is in the variable object "var6". Now, 
when you do "var6 update", it returns either an empty list if its value 
has not changed since the last check OR it returns "var6" if its value 
has changed. Or look in the debug window and it prints "Type changed" all 
the time.

Keith