|
From: Masterson, D. H <dou...@bo...> - 2008-05-20 18:07:42
|
Hi. I'm new to valgrind, so please forgive me if this is an obvious question. I just built valgrind and it always fails when I run it, no matter which program I use as input. It always fails with the same Assertion: valgrind: m_scheduler/sema.c:96 (vgModuleLocal_sema_down): Assertion 'sema->owner_lwpid != lwpid' failed. It looks like I might have something wrong with my configuration, but I have no idea where to start looking. I have tried building valgrind with both gcc 2.96 and gcc 3.4.6, always with the same result. Has anyone seen this behavior before? Thanks, Doug Here is the complete program output: engrarl:dhm>valgrind -v --leak-check=yes cat ==2454== Memcheck, a memory error detector. ==2454== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==2454== Using LibVEX rev 1804, a library for dynamic binary translation. ==2454== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==2454== Using valgrind-3.3.0, a dynamic binary instrumentation framework. ==2454== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==2454== --2454-- Command line --2454-- cat --2454-- Startup, with flags: --2454-- -v --2454-- --leak-check=yes --2454-- Contents of /proc/version: --2454-- Linux version 2.4.9-e.72smp (bhc...@hs...) ( gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Tue Jul 3 22: 04:51 EDT 2007 --2454-- Arch and hwcaps: X86, x86-sse1-sse2 --2454-- Page sizes: currently 4096, max supported 4096 --2454-- Valgrind library directory: /usr/local/lib/valgrind --2454-- Reading syms from /lib/ld-2.2.4.so (0x4000000) --2454-- Reading syms from /bin/cat (0x8048000) --2454-- object doesn't have a symbol table --2454-- Reading syms from /usr/local/lib/valgrind/x86-linux/memcheck (0x3800000 0) --2454-- object doesn't have a dynamic symbol table --2454-- Reading suppressions file: /usr/local/lib/valgrind/default.supp valgrind: m_scheduler/sema.c:96 (vgModuleLocal_sema_down): Assertion 'sema->owne r_lwpid != lwpid' failed. ==2454== at 0x38019CEE: report_and_quit (m_libcassert.c:140) ==2454== by 0x38019B64: vgPlain_assert_fail (m_libcassert.c:200) ==2454== by 0x38038741: vgModuleLocal_sema_down (m_scheduler/sema.c:112) ==2454== by 0x38035803: vgPlain_acquire_BigLock (m_scheduler/scheduler.c:215) ==2454== by 0x380392C0: vgPlain_client_syscall (m_syswrap/syswrap-main.c:947) ==2454== by 0x380366ED: vgPlain_scheduler (m_scheduler/scheduler.c:790) ==2454== by 0x3803A705: run_a_thread_NORETURN (m_syswrap/syswrap-linux.c:89) sched status: running_tid=0 Thread 1: status = VgTs_WaitSys ==2454== at 0x4012344: open (in /lib/ld-2.2.4.so) ==2454== by 0x40079BC: _dl_map_object (dl-load.c:1709) ==2454== by 0x40038BB: dl_main (rtld.c:713) ==2454== by 0x4010296: _dl_sysdep_start (../sysdeps/generic/dl-sysdep.c:208) ==2454== by 0x4002450: _dl_start_final (rtld.c:263) ==2454== by 0x4002242: _dl_start (rtld.c:216) ==2454== by 0x4001EA5: (within /lib/ld-2.2.4.so) 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: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. |
|
From: Bart V. A. <bar...@gm...> - 2008-05-20 19:29:16
|
On Tue, May 20, 2008 at 8:07 PM, Masterson, Douglas H <dou...@bo...> wrote: > valgrind: m_scheduler/sema.c:96 (vgModuleLocal_sema_down): Assertion > 'sema->owner_lwpid != lwpid' failed. > > It looks like I might have something wrong with my configuration, but I > have no idea where to start looking. I have tried building valgrind with > both gcc 2.96 and gcc 3.4.6, always with the same result. Has anyone > seen this behavior before? I'm using Valgrind myself since a long time, and have never encountered the above assertion failure myself. Regarding the compiler version: gcc 2.96 is ancient and is not supported by Valgrind. gcc 3.4.6 should be OK though. Do you get the same error message when you build the Valgrind trunk with gcc 3.4.6 ? See also http://www.valgrind.org/downloads/repository.html for instructions on how to do this. Bart. |