|
From: Srivatsa <sr...@in...> - 2004-04-21 14:05:32
|
Hi , I am getting following output when i ran a "valgrind" on some binary. valgrind version is 2.0.0 output we got is : ==6180== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==6180== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==6180== Using valgrind-2.0.0, a program supervision framework for x86-linux. ==6180== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==6180== Command line: ==6180== ./hponcfg ==6180== Startup, with flags: ==6180== --suppressions=/usr/local/lib/valgrind/default.supp ==6180== -v ==6180== Reading syms from /root/valgrind/valgrind-2.0.0/hponcfg ==6180== Reading syms from /lib/ld-2.2.93.so ==6180== object doesn't have any debug info ==6180== Reading syms from /usr/local/lib/valgrind/vgskin_memcheck.so ==6180== Reading syms from /usr/local/lib/valgrind/valgrind.so ==6180== Reading syms from /usr/lib/libcpqci.so.1.0 ==6180== Reading syms from /lib/i686/libc-2.2.93.so ==6180== object doesn't have any debug info ==6180== Reading suppressions file: /usr/local/lib/valgrind/default.supp ==6180== Estimated CPU clock rate is 2816 MHz ==6180== No RILOE II board found ==6180== Invalid read of size 4 ==6180== at 0x4022B644: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== by 0x8048EF1: probe_mp_device (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== by 0x8048CF7: main (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A018 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022B655: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== by 0x8048EF1: probe_mp_device (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== by 0x8048CF7: main (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A298 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD33: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A084 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD36: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A080 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD41: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A104 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD44: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A100 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD53: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A008 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD69: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A008 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD80: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A184 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD83: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A180 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD8E: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A18C is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD91: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A188 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD9C: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A084 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BD9F: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A080 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDB2: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A104 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDB5: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A100 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDCC: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A184 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDCF: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A180 is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDE6: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A18C is not stack'd, malloc'd or free'd ==6180== ==6180== Invalid read of size 4 ==6180== at 0x4022BDE9: CpqCiFifoDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022C4D9: CpqCiPacketDequeue (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x4022B690: CpqCiSend (in /usr/lib/libcpqci.so.1.0) ==6180== by 0x804A647: ilo_detect_firmflash (in /root/valgrind/valgrind-2.0.0/hponcfg) ==6180== Address 0x4117A188 is not stack'd, malloc'd or free'd disInstr: unhandled instruction bytes: 0xF0 0xF 0xC7 0xF Illegal instruction From the above output it is clear that we are not getting any memory leakage report. Please let me know how to resolve the above issue. Thanks®ards M.S.Srivatsa |
|
From: Maciej P. <uzy...@gm...> - 2007-09-12 20:15:10
|
I try to report a memory leak in someone's else program. However despite it runs well valgrid crash on open: valgrind: the 'impossible' happened: repeated section! ==29325== at 0x38016DAD: report_and_quit (m_libcassert.c:136) ==29325== by 0x38016ECB: panic (m_libcassert.c:210) ==29325== by 0x38016F62: vgPlain_core_panic_at (m_libcassert.c:215) ==29325== by 0x38016F98: vgPlain_core_panic (m_libcassert.c:220) ==29325== by 0x38067ACC: vgModuleLocal_read_elf_debug_info (readelf.c:1193) ==29325== by 0x38036B72: vgPlain_di_notify_mmap (debuginfo.c:207) ==29325== by 0x3804967A: vgModuleLocal_generic_PRE_sys_mmap (syswrap- generic. c:1918) ==29325== by 0x3805FD7F: vgSysWrap_x86_linux_sys_mmap2_before (syswrap- x86-li nux.c:1313) ==29325== by 0x3804E90C: vgPlain_client_syscall (syswrap-main.c:719) ==29325== by 0x38038A27: vgPlain_scheduler (scheduler.c:721) ==29325== by 0x3805BDCB: run_a_thread_NORETURN (syswrap-linux.c:87) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==29325== at 0x4015193: mmap (in /lib/ld-2.6.1.so) ==29325== by 0x40068D2: _dl_map_object_from_fd (dl-load.c:1202) ==29325== by 0x40083E9: _dl_map_object (dl-load.c:2230) ==29325== by 0x400C185: openaux (dl-deps.c:63) ==29325== by 0x400DA31: _dl_catch_error (dl-error.c:178) ==29325== by 0x400C35D: _dl_map_object_deps (dl-deps.c:246) ==29325== by 0x4011AB5: dl_open_worker (dl-open.c:330) ==29325== by 0x400DA31: _dl_catch_error (dl-error.c:178) ==29325== by 0x401145D: _dl_open (dl-open.c:596) ==29325== by 0x51CBC4B: dlopen_doit (dlopen.c:66) ==29325== by 0x400DA31: _dl_catch_error (dl-error.c:178) ==29325== by 0x51CC10B: _dlerror_run (dlerror.c:164) ==29325== by 0x51CBB6B: dlopen@@GLIBC_2.1 (dlopen.c:87) ==29325== by 0x4F5C6B1: g_module_open (gmodule-dl.c:98) (...) Thread 2: status = VgTs_WaitSys ==29325== at 0x53907F7: poll (poll.c:87) ==29325== by 0x4131ED8: PR_Poll (ptio.c:3877) ==29325== by 0x566E818: nsSocketTransportService::Poll(unsigned*) (nsSocketTransportService2.cpp:361) ==29325== by 0x566F00C: nsSocketTransportService::Run() (nsSocketTransportService2.cpp:577) ==29325== by 0x559A7D4: nsThread::Main(void*) (nsThread.cpp:118) ==29325== by 0x4136009: _pt_root (ptthread.c:220) ==29325== by 0x51B917A: start_thread (pthread_create.c:296) ==29325== by 0x5399B1D: clone (in /lib/libc-2.6.1.so) Thread 3: status = VgTs_WaitSys ==29325== at 0x51BD7EC: pthread_cond_timedwait@@GLIBC_2.3.2 (in /lib/ libpthread-2.6.1.so) ==29325== by 0x323E750F: ??? 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. % valgrind --version valgrind-3.2.3 I'm using gentoo. What's wrong? Regards PS. I haven't found anything useful in FAQ. -- I've probably left my head... somewhere. Please wait untill I find it. Homepage (pl_PL): http://uzytkownik.jogger.pl/ (GNU/)Linux User: #425935 (see http://counter.li.org/) |
|
From: Nicholas N. <nj...@ca...> - 2004-04-21 14:19:00
|
On Wed, 21 Apr 2004, Srivatsa wrote: > I am getting following output when i ran a "valgrind" on some > binary. > valgrind version is 2.0.0 > > output we got is : > > [...] > > disInstr: unhandled instruction bytes: 0xF0 0xF 0xC7 0xF > Illegal instruction Try version 2.1.1, it has more complete coverage of x86 instructions. > From the above output it is clear that we are not getting any memory > leakage report. That is not correct; memory leaks are only reported by Memcheck when a program terminates, and that program didn't terminate properly because of the assertion failure. So it's unclear whether you have memory leaks or not. And you need to use the --leak-check=yes flag anyway. N |
|
From: Srivatsa <sr...@in...> - 2004-04-22 09:16:41
|
Hi Nicholas, We have tried using "valgrind 2.1.1" but we are getting a different problem. After installing valgrind 2.1.1, "valgrind ls -l" displays the usage string and it doesn't give any memory leakage report. We did try "valgrind --tool=memcheck ls -l " This gives the following output ==29730== Memcheck, a memory error detector for x86-linux. ==29730== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. ==29730== Using valgrind-2.1.1, a program supervision framework for x86-linux. ==29730== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. --29730-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --29730-- si_code=1 Fault EIP: 0xB025BB90 (); Faulting address: 0x50100000 valgrind: the `impossible' happened: Killed by fatal signal Basic block ctr is approximately 0 ==29730== at 0xB802A143: ??? ==29730== by 0xB802A142: ??? ==29730== by 0xB802A158: ??? ==29730== by 0xB802FA63: ??? sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==29730== at 0x3C000B30: ??? 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@dlilo1 valgrind-2.1.1]# valgrind ls -l usage: valgrind --tool=<toolname> [options] prog-and-args common user options for all Valgrind tools, with defaults in [ ]: --tool=<name> Use the Valgrind tool named <name> --help show this message --help-debug show this message, plus debugging options --version show version -q --quiet run silently; only print error msgs -v --verbose be more verbose, incl counts of errors --trace-children=no|yes Valgrind-ise child processes? [no] --track-fds=no|yes Track open file descriptors? [no] uncommon user options for all Valgrind tools: --run-libc-freeres=no|yes Free up glibc memory at exit? [yes] --weird-hacks=hack1,hack2,... [none] recognised hacks are: ioctl-VTIME truncate-writes lax-ioctls --signal-polltime=<time> time, in mS, we should poll for signals. Only applies for older kernels which need signal routing [50] --lowlat-signals=no|yes improve wake-up latency when a thread receives a signal [no] --lowlat-syscalls=no|yes improve wake-up latency when a thread's syscall completes [no] --pointercheck=no|yes enforce client address space limits [yes] user options for Valgrind tools that report errors: --logfile-fd=<number> file descriptor for messages [2=stderr] --logfile=<file> log messages to <file>.pid<pid> --logsocket=ipaddr:port log messages to socket ipaddr:port --demangle=no|yes automatically demangle C++ names? [yes] --num-callers=<number> show <num> callers in stack traces [4] --error-limit=no|yes stop showing new errors if too many? [yes] --show-below-main=no|yes continue stack traces below main() [no] --suppressions=<filename> suppress errors described in <filename> --gen-suppressions=no|yes print suppressions for errors detected [no] --db-attach=no|yes start debugger when errors detected? [no] --db-command=<command> command to start debugger [gdb -nw %f %p] --input-fd=<number> file descriptor for input [0=stdin] Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc Valgrind is Copyright (C) 2000-2004 Julian Seward and licensed under the GNU General Public License, version 2. Bug reports, feedback, admiration, abuse, etc, to: valgrind.kde.org. Tools are copyright and licensed by their authors. See each tool's start-up message for more information. [root@dlilo1 valgrind-2.1.1]# valgrind --tool=memcheck ls -l ==30226== Memcheck, a memory error detector for x86-linux. ==30226== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. ==30226== Using valgrind-2.1.1, a program supervision framework for x86-linux. ==30226== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. --30226-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --30226-- si_code=1 Fault EIP: 0xB025BB90 (); Faulting address: 0x50100000 valgrind: the `impossible' happened: Killed by fatal signal Basic block ctr is approximately 0 ==30226== at 0xB802A143: ??? ==30226== by 0xB802A142: ??? ==30226== by 0xB802A158: ??? ==30226== by 0xB802FA63: ??? sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==30226== at 0x3C000B30: ??? 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. Whereas in case of valgrind-2.0.0 "valgrind ls -l" works as expected. Please let me know if you have any other suggestion. Thanks®ards M.S.Srivatsa -----Original Message----- From: Nicholas Nethercote [mailto:nj...@he...]On Behalf Of Nicholas Nethercote Sent: Wednesday, April 21, 2004 7:49 PM To: Srivatsa Cc: val...@li... Subject: Re: [Valgrind-users] Problem with valgrind On Wed, 21 Apr 2004, Srivatsa wrote: > I am getting following output when i ran a "valgrind" on some > binary. > valgrind version is 2.0.0 > > output we got is : > > [...] > > disInstr: unhandled instruction bytes: 0xF0 0xF 0xC7 0xF > Illegal instruction Try version 2.1.1, it has more complete coverage of x86 instructions. > From the above output it is clear that we are not getting any memory > leakage report. That is not correct; memory leaks are only reported by Memcheck when a program terminates, and that program didn't terminate properly because of the assertion failure. So it's unclear whether you have memory leaks or not. And you need to use the --leak-check=yes flag anyway. N |
|
From: Lee D. <lee...@mi...> - 2004-04-22 17:06:12
|
Please let me know if you solve this one as my 2.1.1 also behaves the same. > -----Original Message----- > From: val...@li... > [mailto:val...@li...]On Behalf > Of Srivatsa > Sent: Thursday, April 22, 2004 1:44 AM > To: 'Nicholas Nethercote' > Cc: val...@li...; ra...@in...; > sr...@in... > Subject: RE: [Valgrind-users] Problem with valgrind > > > Hi Nicholas, > We have tried using "valgrind 2.1.1" but we are getting a different > problem. > After installing valgrind 2.1.1, > "valgrind ls -l" displays the usage string and it doesn't > give any memory > leakage > report. > We did try > "valgrind --tool=memcheck ls -l " This gives the following output > > ==29730== Memcheck, a memory error detector for x86-linux. > ==29730== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. > ==29730== Using valgrind-2.1.1, a program supervision framework for > x86-linux. > ==29730== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. > --29730-- INTERNAL ERROR: Valgrind received a signal 11 > (SIGSEGV) - exiting > --29730-- si_code=1 Fault EIP: 0xB025BB90 (); Faulting > address: 0x50100000 > > valgrind: the `impossible' happened: > Killed by fatal signal > Basic block ctr is approximately 0 > ==29730== at 0xB802A143: ??? > ==29730== by 0xB802A142: ??? > ==29730== by 0xB802A158: ??? > ==29730== by 0xB802FA63: ??? > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==29730== at 0x3C000B30: ??? > > > 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@dlilo1 valgrind-2.1.1]# valgrind ls -l > usage: valgrind --tool=<toolname> [options] prog-and-args > > common user options for all Valgrind tools, with defaults in [ ]: > --tool=<name> Use the Valgrind tool named <name> > --help show this message > --help-debug show this message, plus > debugging options > --version show version > -q --quiet run silently; only print error msgs > -v --verbose be more verbose, incl counts of errors > --trace-children=no|yes Valgrind-ise child processes? [no] > --track-fds=no|yes Track open file descriptors? [no] > > uncommon user options for all Valgrind tools: > --run-libc-freeres=no|yes Free up glibc memory at exit? [yes] > --weird-hacks=hack1,hack2,... [none] > recognised hacks are: ioctl-VTIME truncate-writes lax-ioctls > --signal-polltime=<time> time, in mS, we should poll for signals. > Only applies for older kernels > which need > signal routing [50] > --lowlat-signals=no|yes improve wake-up latency when a > thread receives > a signal [no] > --lowlat-syscalls=no|yes improve wake-up latency when a thread's > syscall completes [no] > --pointercheck=no|yes enforce client address space > limits [yes] > > user options for Valgrind tools that report errors: > --logfile-fd=<number> file descriptor for messages [2=stderr] > --logfile=<file> log messages to <file>.pid<pid> > --logsocket=ipaddr:port log messages to socket ipaddr:port > --demangle=no|yes automatically demangle C++ names? [yes] > --num-callers=<number> show <num> callers in stack traces [4] > --error-limit=no|yes stop showing new errors if too > many? [yes] > --show-below-main=no|yes continue stack traces below main() [no] > --suppressions=<filename> suppress errors described in <filename> > --gen-suppressions=no|yes print suppressions for errors > detected [no] > --db-attach=no|yes start debugger when errors > detected? [no] > --db-command=<command> command to start debugger [gdb > -nw %f %p] > --input-fd=<number> file descriptor for input [0=stdin] > > > Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc > > Valgrind is Copyright (C) 2000-2004 Julian Seward > and licensed under the GNU General Public License, version 2. > Bug reports, feedback, admiration, abuse, etc, to: valgrind.kde.org. > > Tools are copyright and licensed by their authors. See each > tool's start-up message for more information. > > [root@dlilo1 valgrind-2.1.1]# valgrind --tool=memcheck ls -l > ==30226== Memcheck, a memory error detector for x86-linux. > ==30226== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. > ==30226== Using valgrind-2.1.1, a program supervision framework for > x86-linux. > ==30226== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. > --30226-- INTERNAL ERROR: Valgrind received a signal 11 > (SIGSEGV) - exiting > --30226-- si_code=1 Fault EIP: 0xB025BB90 (); Faulting > address: 0x50100000 > > valgrind: the `impossible' happened: > Killed by fatal signal > Basic block ctr is approximately 0 > ==30226== at 0xB802A143: ??? > ==30226== by 0xB802A142: ??? > ==30226== by 0xB802A158: ??? > ==30226== by 0xB802FA63: ??? > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==30226== at 0x3C000B30: ??? > > > 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. > > Whereas in case of valgrind-2.0.0 "valgrind ls -l" works as > expected. > > Please let me know if you have any other suggestion. > Thanks®ards > M.S.Srivatsa > -----Original Message----- > From: Nicholas Nethercote [mailto:nj...@he...]On Behalf Of > Nicholas Nethercote > Sent: Wednesday, April 21, 2004 7:49 PM > To: Srivatsa > Cc: val...@li... > Subject: Re: [Valgrind-users] Problem with valgrind > > > On Wed, 21 Apr 2004, Srivatsa wrote: > > > I am getting following output when i ran a "valgrind" on some > > binary. > > valgrind version is 2.0.0 > > > > output we got is : > > > > [...] > > > > disInstr: unhandled instruction bytes: 0xF0 0xF 0xC7 0xF > > Illegal instruction > > Try version 2.1.1, it has more complete coverage of x86 instructions. > > > From the above output it is clear that we are not getting > any memory > > leakage report. > > That is not correct; memory leaks are only reported by > Memcheck when a > program terminates, and that program didn't terminate > properly because of > the assertion failure. So it's unclear whether you have > memory leaks or > not. And you need to use the --leak-check=yes flag anyway. > > N > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |