|
From: Lee D. <lee...@mi...> - 2004-04-16 18:30:27
|
No takers? This error happens on anything I try. tool=memcheck, tool=helgrind, whatever. -lee > -----Original Message----- > From: Lee Dilkie [mailto:lee...@mi...] > Sent: Thursday, April 15, 2004 12:51 PM > To: 'Nicholas Nethercote' > Cc: 'val...@li...' > Subject: RE: [Valgrind-users] does valgrind not recover deleted > semaphores? > > > > What goes wrong? Can you show the output of "valgrind -v" > > for a sample > > prog, plus the output of "uname -a"? Thanks. > > [root@localhost TUG]# uname -a > Linux localhost.localdomain 2.4.18-27.7.x #1 Fri Mar 14 > 06:44:53 EST 2003 i686 unknown > > [root@localhost TUG]# valgrind -v --tool=memcheck ls > ==13655== Memcheck, a memory error detector for x86-linux. > ==13655== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. > ==13655== Using valgrind-2.1.2.CVS, a program supervision > framework for x86-linux. > ==13655== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. > ==13655== Valgrind library directory: /usr/local/lib/valgrind > ==13655== Command line > ==13655== ls > ==13655== Startup, with flags: > ==13655== -v > ==13655== --tool=memcheck > ==13655== Reading syms from /bin/ls (0x8048000) > ==13655== object doesn't have a symbol table > ==13655== object doesn't have any debug info > --13655-- INTERNAL ERROR: Valgrind received a signal 11 > (SIGSEGV) - exiting > --13655-- si_code=1 Fault EIP: 0xB030B4BC (); Faulting > address: 0x50100000 > > valgrind: the `impossible' happened: > Killed by fatal signal > Basic block ctr is approximately 0 > ==13655== at 0xB802BF5F: ??? > ==13655== by 0xB802BF5E: ??? > ==13655== by 0xB802BF74: ??? > ==13655== by 0xB803288F: ??? > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==13655== at 0x3C000B50: ??? > > > 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. > > [root@localhost TUG]# > |