Re: [Valgrind-users] valgrind problem

[Bob R. <bo...@br...>]

On Mon, Nov 01, 2004 at 05:22:53PM -0500, Bob Rossi wrote:
> On Mon, Nov 01, 2004 at 08:14:45PM +0000, Tom Hughes wrote:
> > In message <20041101185938.GE2460@white>
> >           Bob Rossi <bo...@br...> wrote:
> > 
> > > 
> > > Thanks Tom,
> > > 
> > > I found the place where it is looping forever, it is in vg_symtypes.c
> > > line 416.
> > > 
> > > Here is the backtrace.
> > > 
> > > #0  vgPlain_st_basetype (type=0xb0201498, do_resolve=0 '\0') at
> > > vg_symtypes.c:41
> > > 7
> > > #1  0xb0037778 in initSym (si=0xb01e8020, sym=0xb0200f58, kind=N_LSYM,
> > > namep=0xb
> > > fffeaa0, val=0) at vg_stabs.c:1095
> > > #2  0xb00382b0 in vgPlain_read_debuginfo_stabs (si=0xb01e8020,
> > > stabC=0xb02fbf20
> > > "\001", stab_sz=29508, stabstr=0xb0303264 "", stabstr_sz=61536) at
> > > vg_stabs.c:16
> > > 72
> > > 
> > > 
> > > Basically the typdef points to itself.
> > > 
> > > $8 = (SymType *) 0xb0201430
> > > (tgdb) p type->u.t_typedef.type
> > > $9 = (SymType *) 0xb0201430
> > > (tgdb)
> > 
> > That looks suspiciously like the bug I fixed a few weeks ago. Are
> > you using the CVS head or 2.2.0 here?
> 
> I was using CVS from sometime around a few weeks ago :)
> I'll do an update and try again. Hopefully it'll work ...

Great, this works now, thanks!

Bob Rossi