RE: (Another) Segfault in varobj.c

["Robert Norton" <rnorton@broadcom.com>]

> -----Original Message-----
> From: gdb-owner@sourceware.org 
> [mailto:gdb-owner@sourceware.org] On Behalf Of Robert Norton
> Sent: 07 August 2007 17:11
> To: Vladimir Prus; gdb@sources.redhat.com
> Subject: RE: (Another) Segfault in varobj.c
>
> I'll give it a try!

For anyone who's interested I managed to back port the changes by
copying varobj.c/h and mi/*. I had to edit mi-main.c to get it to
compile (used current_regcache instead of get_current_regcache()) and
also had to add a call to varobj_invalidate() in symfile.c.

I also had a problem with one of the tests: mi-var-cmd.exp creates a
varobj from a char* but due to gdb interpreting it is a null terminated
string it appears to be modified even though it is actually the llong
variable which is allocated after it in memory which has changed. What's
needed is some way to tell gdb that lpcharacter really is just a char *
(not a pointer to a null terminated string).

Robert