RE: Segfault in varobj.c

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

 

> -----Original Message-----
> From: Nick Roberts [mailto:nickrob@snap.net.nz] 
> Sent: 27 July 2007 12:52
> To: Robert Norton
> Cc: gdb@sourceware.org
> Subject: Re: Segfault in varobj.c
> 
> Robert Norton writes:
>  > Hi,
>  > 
>  > I encountered a segfault whilst using our port of GDB with 
> Eclipse. It
>  > occurs when I add a number of global variables in the 
> variables view and
>  > expand them. Occasionally I observe something like the 
> following in the
>  > MI console:
>  > 
>  > (gdb) 
>  > 2247-var-list-children
>  > 
> var2.tx_ready_next.tx_ready_next.tx_ready_next.tx_suspended_ne
> xt.tx_thre
>  > ad_name
>  > warning: Child of parent whose type does not allow children
>  > &"warning: Child of parent whose type does not allow children\n"
>  > 
>  > Followed by gdb segfaulting. On loading the core file I observe:
> 
> It might be more useful to set the breakpoint on the line 
> where the initial
> warning was issued.

Yes. After submitting the post I found where the warning was coming from
and am investigating. I can now reproduce reliably so am distilling down
to a minimal recipe for generating the bug, which hopefully will shed
some light.
 
> 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.

Robert

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