|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2004-08-26 09:24:47
|
Hi, I'm running Valgrind 2.1.2 on Red Hat 9. I'm using it to debug some not always reproducible crashes in program distcc 2.17 under high load. I've replaced program distcc by a script that launches distcc under Valgrind. 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. Note that the distcc stack probably gets corrupted: I couldn't get meaningful stack traces from the core files in any debugger. ==10615== Memcheck, a memory error detector for x86-linux. ==10615== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al. ==10615== Using valgrind-2.1.2, a program supervision framework for x86-linux. ==10615== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. ==10615== For more details, rerun with: -v ==10615== distcc[10615] ERROR: Connect timeout 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) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==10615== at 0x52BFE0A4: ??? Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: valgrind.kde.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. Regards, Dimitri |