|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2004-08-26 10:05:14
|
Hi, >>But now Valgrind crashes with the following message. Is this a known >>issue, or should I file in a bug? I wasn't able to relate this crash >>to any of the FAQ items. > > > Please file a bug. >>valgrind: vg_to_ucode.c:5285 (disInstr): Assertion `abyte == 0' failed. >>==10615== at 0xB002AA26: vgPlain_skin_assert_fail (vg_mylibc.c:1169) >>==10615== by 0xB002AA25: assert_fail (vg_mylibc.c:1165) >>==10615== by 0xB002AA63: vgPlain_core_assert_fail (vg_mylibc.c:1176) >>==10615== by 0xB00511DA: disInstr (vg_to_ucode.c:7300) > > > That's an ENTER instruction with a non-zero nesting level. It sounds > like a pretty unusual instruction to be using - are you sure your program > isn't jumping through a bad pointer somewhere? Alas, it's not my program: http://distcc.samba.org/ The crash probably occurs in some error handling routine, since it happens after this message: distcc[10615] ERROR: Connect timeout Since I don't know where distcc crashes, it's hard to tell what the actual code looks like. Note that I have some 40 instances of distcc running in parallel under Valgrind. Among those distcc instances that crash, some of them will cause Valgrind to crash at exactly the same vg_to_ucode.c line, others won't. Regards, Dimitri |