|
From: Tom H. <th...@cy...> - 2004-09-13 11:46:29
|
In message <Pin...@he...>
Nicholas Nethercote <nj...@ca...> wrote:
> On Mon, 13 Sep 2004, Nicholas Nethercote wrote:
>
>>> I had posted earlier about valgrind stalling but
>>> since nobody seemed to have encountered it I decided
>>> to try investigating myself. I turned on some of the
>>> debug flags and added some printf statements at some
>>> points in the code. I find that valgrind is going into
>>> an infinite loop in one place. These are the debug
>>> statements before it stalls
>>> initSym(si=0xB02ED020, tab=0xB02FD120, sym=0xB17416F8,
>>> kind=128, name=0xB0AC6C46 "msgbuf:Tt(0,27)=xsmsgbuf:",
>>> val=0)
>>> initSym name="msgbuf" type=Tt(0,27)=xsmsgbuf:
>>> initSym: before base type
>>> I added the following printfs in vg_stabs.c
>>> VG_(printf)("initSym: before base type\n");
>>> base = VG_(st_basetype)(sym->type, False);
>>> VG_(printf)("initSym: after base type\n");
>>> As can be seen from the logs I dont get anything
>>> printed after "..before base type..". It is just
>>> spinning in VG_(st_basetype).
>>
>> Can you file a bug report for this please?
>
> Actually, it might be more appropriate to add a comment to
> http://bugs.kde.org/show_bug.cgi?id=88703 explaining your situation (I
> think that's the bug you're talking about?)
Why? That bug isn't about a stall, it's about a warning from
the stabs reader. I'm not aware of any reason to believe that
the two are linked.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|