|
From: John R. <joh...@cr...> - 2004-03-16 21:06:51
|
Memcheck in Valgrind 2.1.1 doesn't work on my
program, while the 2.1.0 distro did.
I'm running the 2.4.21 kernel on Redhat Enterprise
Linux 3. I made two "tweaks" to valgrind that might
of affected this. :)
I upped two values in coregrind/vg_include.h:
#define M_PROCMAP_BUF 500000
(was 50000)
#define VG_N_SEMAPHORES 250
(was 50)
I upped those values because I ran into these limits
in some earlier version of Valgrind.
The gory details are appended...
John Roberts
Credence Systems Corporation
95 mexia(2.4.21-4.0.1.EL):jroberts:server>
/export/jroberts/valgrind/latest/bin/valgrind --tool=memcheck -v .vserver_g
==4641== Memcheck, a memory error detector for x86-linux.
==4641== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==4641== Using valgrind-2.1.1, a program supervision framework for x86-linux.
==4641== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==4641== Valgrind library directory:
/export/jroberts/valgrind/latest/lib/valgrind
==4641== Command line
==4641== .vserver_g
==4641== Startup, with flags:
==4641== --tool=memcheck
==4641== -v
==4641== Reading syms from /export/jroberts/c/ServerApps/src/server/.vserver_g
(0x8048000)
==4641== Reading syms from /lib/ld-2.3.2.so (0x3C000000)
==4641== object doesn't have any debug info
==4641== Reading syms from /lib/ld-2.3.2.so (0xB0000000)
==4641== object doesn't have any debug info
==4641== Reading syms from
/export/jroberts/valgrind/latest/lib/valgrind/vgskin_memcheck.so (0xB728D000)
==4641== Reading syms from /lib/tls/libc-2.3.2.so (0xB74B5000)
==4641== object doesn't have any debug info
==4641== Reading syms from /lib/libdl-2.3.2.so (0xB75ED000)
==4641== object doesn't have any debug info
==4641== Reading syms from /export/jroberts/valgrind/latest/lib/valgrind/stage2
(0xB8000000)
==4641== Reading suppressions file:
/export/jroberts/valgrind/latest/lib/valgrind/default.supp
==4641== REDIRECT soname:libc.so.6(__GI___errno_location) to
soname:libpthread.so.0(__errno_location)
==4641== REDIRECT soname:libc.so.6(__errno_location) to
soname:libpthread.so.0(__errno_location)
==4641== REDIRECT soname:libc.so.6(__GI___h_errno_location) to
soname:libpthread.so.0(__h_errno_location)
==4641== REDIRECT soname:libc.so.6(__h_errno_location) to
soname:libpthread.so.0(__h_errno_location)
==4641== REDIRECT soname:libc.so.6(__GI___res_state) to
soname:libpthread.so.0(__res_state)
==4641== REDIRECT soname:libc.so.6(__res_state) to
soname:libpthread.so.0(__res_state)
==4641== REDIRECT soname:libc.so.6(stpcpy) to *vgpreload_memcheck.so*(stpcpy)
==4641== REDIRECT soname:libc.so.6(strnlen) to *vgpreload_memcheck.so*(strnlen)
==4641== REDIRECT soname:ld-linux.so.2(stpcpy) to
*vgpreload_memcheck.so*(stpcpy)
==4641== REDIRECT soname:ld-linux.so.2(strchr) to
*vgpreload_memcheck.so*(strchr)
==4641==
==4641== Reading syms from
/export/jroberts/valgrind/latest/lib/valgrind/vg_inject.so (0x3C019000)
==4641== Reading syms from
/export/jroberts/valgrind/latest/lib/valgrind/vgpreload_memcheck.so (0x3C01C000)
==4641== TRANSLATE: 0x3C011E90 redirected to 0x3C01DA00
==4641== Reading syms from
/ims/cobalt/release/linux/subp/TestStation/1_0_Build_17/src/libTestStationS_g.so
(0x3C022000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Ar/1_0_Build_17/src/levels/libLevelsS_g.so
(0x3C2A7000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Ar/1_0_Build_17/src/parameter/libParametersS_g.so
(0x3C582000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Ar/1_0_Build_17/src/command/libCommandS_g.so
(0x3C76D000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Pattern/1_0_Build_17/src/libPatternS_g.so
(0x3C841000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Ar/1_0_Build_17/src/timing/libTimingS_g.so
(0x3D58B000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Sync/1_0_Build_17/src/libSyncS_g.so (0x3D9EE000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/continuity/libContinu
ityTestS_g.so (0x3DC76000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/functional/vanguard/l
ibFunctionalTestS_g.so (0x3DE52000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/pmu/libPmuTestS_g.so
(0x3DF26000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/search/libSearchTestS
_g.so (0x3E240000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/waves/vanguard/libWav
esTestS_g.so (0x3E384000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/DeviceTest/1_0_Build_17/src/deviceTest/libDeviceT
estS_g.so (0x3E469000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Packet/1_0_Build_17/src/libPacketS_g.so
(0x3E5E1000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Ar/1_0_Build_17/src/device/libDeviceS_g.so
(0x3E62B000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Collections/1_0_Build_17/src/setup/libCollections
SetupS_g.so (0x3EA1A000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Collections/1_0_Build_17/src/layout/libCollection
sLayoutS_g.so (0x3EB54000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Collections/1_0_Build_17/src/result/libCollection
sResultS_g.so (0x3EC13000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Collections/1_0_Build_17/src/foundation/libCollec
tionsFoundationS_g.so (0x3EC98000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Protocol/1_0_Build_17/src/libProtocolS_g.so
(0x3EDFD000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Vtr/1_0_Build_17/src/libVtr_g.so (0x3EE87000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/diagnostics/vanguard/foundati
on/libTrDiagFoundationS_g.so (0x3F06C000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/diagnostics/vanguard/timingMo
dule/libTrDiagTimingModule_g.so (0x3F0D4000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/diagnostics/vanguard/dataModu
le/libTrDiagDataModule_g.so (0x3F136000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/diagnostics/vanguard/cobaltMo
dules/libTrDiagCobaltModules_g.so (0x3F17D000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/calibration/vanguard/libTrCal
ibration_g.so (0x3F1B8000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/testControl/vanguard/libTrTes
tControl_g.so (0x3F268000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/setup/vanguard/libTrSetup_g.s
o (0x3F2F9000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/foundation/vanguard/libTrFoun
dation_g.so (0x3F35F000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/hardware/libTrHardware_g.so
(0x3F396000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Tr/1_0_Build_17/src/adsp21kElf/libTrAdsp21kElf_g.
so (0x3F698000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Foundation/1_0_Build_17/src/notify/vanguard/libVa
nguardNotifyS_g.so (0x3F6E0000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Foundation/1_0_Build_17/src/foundation/libFoundat
ionS_g.so (0x3F716000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Foundation/1_0_Build_17/src/event/libEvent_g.so
(0x3F7B1000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Foundation/1_0_Build_17/src/enumeration/libEnumS_
g.so (0x3F89E000)
==4641== Reading syms from
/ims/cobalt/release/linux/subp/Foundation/1_0_Build_17/src/support/vanguard/libS
upport_g.so (0x3F944000)
==4641== Reading syms from
/ims/core/release/linux/subp/Core/X3_07A/lib/libCoreS_g.so (0x3F98A000)
==4641== Reading syms from
/export/jroberts/valgrind/latest/lib/valgrind/libpthread.so (0x40238000)
==4641== Reading syms from /lib/libdl-2.3.2.so (0x4027A000)
==4641== object doesn't have any debug info
==4641== Reading syms from /lib/libnsl-2.3.2.so (0x4027E000)
==4641== object doesn't have any debug info
==4641== Reading syms from /lib/tls/libm-2.3.2.so (0x40296000)
==4641== object doesn't have any debug info
==4641== Reading syms from /lib/tls/libc-2.3.2.so (0x402B9000)
==4641== object doesn't have any debug info
--4641-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--4641-- si_code=1 Fault EIP: 0xB8025D66; Faulting address: 0xBFF25004
valgrind: the `impossible' happened:
Killed by fatal signal
Basic block ctr is approximately 43050000
==4641== at 0xB802A070: vgPlain_core_panic (vg_mylibc.c:1230)
==4641== by 0xB802A06F: panic (vg_mylibc.c:1226)
==4641== by 0xB802A084: vgPlain_core_panic (vg_mylibc.c:1231)
==4641== by 0xB802F936: vg_sync_signalhandler (vg_signals.c:1756)
sched status:
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
valgrind: ../../valgrind-2.1.1/coregrind/vg_mylibc.c:1681
(vgPlain_get_memory_from_mmap): Assertion `p >= (void
*)vgPlain_valgrind_mmap_end && p < (void *)vgPlain_valgrind_end' failed.
==4641== at 0xB802A001: vgPlain_skin_assert_fail (vg_mylibc.c:1211)
==4641== by 0xB802A000: assert_fail (vg_mylibc.c:1207)
==4641== by 0xB802A03E: vgPlain_core_assert_fail (vg_mylibc.c:1218)
==4641== by 0xB802A8CC: vgPlain_get_memory_from_mmap (vg_mylibc.c:1681)
sched status:
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
96 mexia(2.4.21-4.0.1.EL):jroberts:server> uname -a
Linux mexia 2.4.21-4.0.1.EL #1 Thu Oct 23 01:36:33 EDT 2003 i686 i686 i386
GNU/Linux
97 mexia(2.4.21-4.0.1.EL):jroberts:server> cat /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon)
|
|
From: Jeremy F. <je...@go...> - 2004-03-16 22:26:31
|
On Tue, 2004-03-16 at 13:06, John Roberts wrote: > Memcheck in Valgrind 2.1.1 doesn't work on my > program, while the 2.1.0 distro did. > > I'm running the 2.4.21 kernel on Redhat Enterprise > Linux 3. I made two "tweaks" to valgrind that might > of affected this. :) > I upped two values in coregrind/vg_include.h: > > #define M_PROCMAP_BUF 500000 > (was 50000) > > #define VG_N_SEMAPHORES 250 > (was 50) > > I upped those values because I ran into these limits > in some earlier version of Valgrind. > > The gory details are appended... Hm, looks like its running out of heap. Is that a large number of .so files of C++ code compiled with -g? Try increasing the heap size by changing VALGRIND_HEAPSIZE in vg_main.c - try 256M or something. J |