Menu
▾
▴
[Valgrind-users] Problem running valgrind stored in Rational ClearCase
|
From: Dominik S. <dst...@ft...> - 2004-01-12 14:22:42
|
Hi, I don't think valgrind is responsible, but I thought I'd report it anyway, maybe you can add sort of a "Known Issue" somewhere. When I try to run the valgrind-binaries stored in the Rational/IBM ClearCase version control-system, valgrind does not work any more: /dcaclearcase/vobs/eParty/valgrind/Bin/Linux/bin/valgrind --leak-check=yes -v \ --num-callers=20 --track-fds=yes TestRunner ==24043== Memcheck, a memory error detector for x86-linux. ==24043== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==24043== Using valgrind-2.1.0, a program supervision framework for x86-linux. ==24043== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==24043== Command line ==24043== TestRunner ==24043== Startup, with flags: ==24043== --suppressions=/dcaclearcase/vobs/eParty/valgrind/Bin/Linux/lib/valgrind/default.supp ==24043== --leak-check=yes ==24043== -v ==24043== --num-callers=20 ==24043== --track-fds=yes ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/80001a863fb03f20TestRunner ==24043== Reading syms from /lib/ld-2.2.4.so ==24043== Reading syms from /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e ==24043== Reading syms from /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/6/21/eb7ef003450311d89c82000180e4a89e ==24043== Reading syms from /lib/i686/libpthread-0.9.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800005e03fb0477dlibTestUnit.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800001cd3fb046dclibFTI_Core.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/80000a473fb03f1flibFTIDBApplication.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800002993fb03ed7libFTIApplication.so ==24043== Reading syms from /lib/libdl-2.2.4.so ==24043== Reading syms from /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so ==24043== Reading syms from /lib/i686/libm-2.2.4.so ==24043== Reading syms from /lib/i686/libc-2.2.4.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800001f23fb0477clibFTI_OS.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800009a23fb046d8libFTI_Nana.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800004843fb046b1libFTIDebug.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800003723fb04761libFTI_Config.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/8000022a3fb0477blibFTI_STL.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800021553fb03ed4libFTI_XMLTree.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800003193fb03ec2libFTI_Datatypes.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/80002b0d3fb03ed6libFTI_XMLConsoleProtocols.so ==24043== Reading syms from /export/home/VIEWS/dstadler_Linux.vws/.s/00011/800004833fafddfblibxerces-c.so ==24043== Reading suppressions file: /dcaclearcase/vobs/eParty/valgrind/Bin/Linux/lib/valgrind/default.supp ==24043== Estimated CPU clock rate is 864 MHz ==24043== ==24043== Warning: segment-override prefix encountered, but thread has no LDT ==24043== Warning: segment access: virtual addr 0 exceeds segment limit of 0 ==24043== Invalid read of size 4 ==24043== at 0x40249EF4: __pthread_alt_lock (spinlock.c:446) ==24043== by 0x40246D25: __pthread_mutex_lock (mutex.c:120) ==24043== by 0x403AE6D0: __register_frame_info (in /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so) ==24043== by 0x40021A61: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x400217D0: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x4000DAA6: _dl_init (dl-init.c:70) ==24043== by 0x40001ED0: (within /lib/ld-2.2.4.so) ==24043== Address 0x0 is not stack'd, malloc'd or free'd ==24043== ==24043== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==24043== Address not mapped to object at address 0x0 ==24043== at 0x40249EF4: __pthread_alt_lock (spinlock.c:446) ==24043== by 0x40246D25: __pthread_mutex_lock (mutex.c:120) ==24043== by 0x403AE6D0: __register_frame_info (in /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so) ==24043== by 0x40021A61: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x400217D0: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x4000DAA6: _dl_init (dl-init.c:70) ==24043== by 0x40001ED0: (within /lib/ld-2.2.4.so) ==24043== ==24043== FILE DESCRIPTORS: 3 open at exit. ==24043== Open file descriptor 2: /dev/pts/2 ==24043== <inherited from parent> ==24043== ==24043== Open file descriptor 1: /dev/pts/2 ==24043== <inherited from parent> ==24043== ==24043== Open file descriptor 0: /dev/pts/2 ==24043== <inherited from parent> ==24043== ==24043== ==24043== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ==24043== ==24043== 1 errors in context 1 of 1: ==24043== Invalid read of size 4 ==24043== at 0x40249EF4: __pthread_alt_lock (spinlock.c:446) ==24043== by 0x40246D25: __pthread_mutex_lock (mutex.c:120) ==24043== by 0x403AE6D0: __register_frame_info (in /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so) ==24043== by 0x40021A61: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x400217D0: (within /.automount/dcaclust2/root/dcaclearcase/VOBS/eParty.vbs/c/cdft/11/41/ee7ef167450311d89c82000180e4a89e) ==24043== by 0x4000DAA6: _dl_init (dl-init.c:70) ==24043== by 0x40001ED0: (within /lib/ld-2.2.4.so) ==24043== Address 0x0 is not stack'd, malloc'd or free'd ==24043== IN SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ==24043== ==24043== malloc/free: in use at exit: 0 bytes in 0 blocks. ==24043== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==24043== ==24043== No malloc'd blocks -- no leaks are possible. --24043-- TT/TC: 0 tc sectors discarded. --24043-- 42 chainings, 0 unchainings. --24043-- translate: new 107 (1859 -> 23983; ratio 129:10) --24043-- discard 0 (0 -> 0; ratio 0:10). --24043-- dispatch: 447 jumps (bb entries), of which 107 (23%) were unchained. --24043-- 1/108 major/minor sched events. 107 tt_fast misses. --24043-- reg-alloc: 16 t-req-spill, 4574+134 orig+spill uis, 527 total-reg-r. --24043-- sanity: 2 cheap, 1 expensive checks. --24043-- ccalls: 421 C calls, 58% saves+restores avoided (1448 bytes) --24043-- 530 args, avg 0.84 setup instrs each (168 bytes) --24043-- 0% clear the stack (1260 bytes) --24043-- 206 retvals, 22% of reg-reg movs avoided (88 bytes) proxy 24049 for tid 1 exited status -1, res 0 /export/home/dstadler/bin/valgrind: line 2: 24043 Segmentation fault /dcaclearcase/vobs/eParty/valgrind/Bin/Linux/bin/valgrind --leak-check=yes -v --num-callers=20 --track-fds=yes $* when the binaries are not stored in ClearCase, valgrind works perfectly. It even works if the valgrind-binary is located inside ClearCase as so called "private files" (i.e. not checked in). The binaries that I try to check can be located in ClearCase, though. Dominik. |
