(Another) Segfault in varobj.c

[Daniel Jacobowitz]

On Wed, Aug 08, 2007 at 10:59:56AM -0700, Robert Norton wrote:
> 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).

Or not to treat it as a string (I have some posted work in that area)
or just to NUL terminate it...

-- 
Daniel Jacobowitz
CodeSourcery