RE: Segfault in varobj.c

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

> -----Original Message-----
> From: Nick Roberts [mailto:nickrob@snap.net.nz] 
> Sent: 27 July 2007 13:16
> To: Robert Norton
> Cc: gdb@sourceware.org
> Subject: RE: Segfault in varobj.c
> 
>  > > This is your port of GDB and it's based on an old 
> version of FSF GDB.
>  > > Does it happen with FSF GDB or, at least, your port 
> based on up-to-date
>  > > FSF GDB?
>  > 
>  > The port is based on GDB 6.6.
> 
> By up-to-date I meant GDB in CVS.  Presumably you could merge 
> your changes to
> that.  It may be that the problem has already been solved or 
> no longer exists
> in the repository.

Ah yes, I see there are quite a lot of changes to the varobjs file. In
particular the warning is no longer present. Unfortunately we're not
really in a position to upgrade to fix such a trivial bug, but due to my
analysis below I think the bug might still occur:

Breakpointing in c_type_of_child (now c_describe_child) we end up in the
default case of the switch because the parent has type code
TYPE_CODE_TYPEDEF, so could it be that the switch requires another case
to handle this situation? I'll see if I can come up with a minimal test
binary based on this.

Thanks,

Robert

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