RE: [patch] Fix for varobj.c assertions.

[Nick Roberts <nickrob@snap.net.nz>]

 > > Can anybody else duplicate this problem? (see pr2309)
 > > 
 > 
 > I did some more testing, it turns out it depends on the toolchain version.
 > 
 > Toolchain that produced the problem:
 > gcc 4.1.1
 > binutils 2.17
 > 
 > However, with
 > gcc 4.1.2
 > binutils 2.18
 > the problem does not reproduce.
 > 
 > 
 > The patch fixes the problem in the case of problematic toolchain version.

Maybe it cures the symptom and not the cause.  We really need to know what is
happening here.  In your oringinal report the failed assertion occurred in
my_value_equal but that function has gone now.  Presumably it now occurs in
install_new_value, but at which line?

When there is no problem, presumably *value (in adjust_value_for_child_access)
or value (in c_describe_child) are null.  How do they become non null for
inaccessible memory in the failing case?

-- 
Nick                                           http://www.inet.net.nz/~nickrob