Re: memory debugging and C++ (program keeps crashing)
On Tue, Oct 01, 2002 at 08:12:29AM +0200, Cyrille Chepelov wrote:
> please upgrade to 1.0.3 (in sid for the moment). The 1.0.X series is a
> bugfix-only serie.
Different error now:
==25618== valgrind-1.0.3, a memory error detector for x86 GNU/Linux.
==25618== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==25618== Estimated CPU clock rate is 846 MHz
==25618== For more details, rerun with: -v
==25618==
==25618== pthread_mutex_unlock: mutex is not locked
==25618== at 0x4049773F: __pthread_mutex_unlock
(/tmp/buildd/valgrind-1.0.3/vg_libpthread.c:837)
==25618== by 0x40323F55: (within /usr/lib/libgnomemm-1.2.so.9.0.3)
==25618== by 0x400473C2: (within /usr/lib/valgrind/valgrind.so)
==25618== by 0x40047265: (within /usr/lib/valgrind/valgrind.so)
==25618==
==25618== pthread_mutex_destroy: mutex is still in use
==25618== at 0x40496978: pthread_error
(/tmp/buildd/valgrind-1.0.3/vg_libpthread.c:233)
==25618== by 0x404977A1: __pthread_mutex_destroy
(/tmp/buildd/valgrind-1.0.3/vg_libpthread.c:854)
==25618== by 0x40AA4940: (within /lib/libc-2.2.5.so)
==25618== by 0x40AA28F7: (within /lib/libc-2.2.5.so)
==25618==
==25618== Syscall param write(buf) contains uninitialised or
unaddressable byte(s)
==25618== at 0x40AFC404: (within /lib/libc-2.2.5.so)
==25618== by 0x4065C98B: (within /usr/X11R6/lib/libICE.so.6.3)
==25618== by 0x4065D653: (within /usr/X11R6/lib/libICE.so.6.3)
==25618== by 0x406551FC: (within /usr/X11R6/lib/libICE.so.6.3)
==25618== Address 0x41EF4EC7 is 3 bytes inside a block of size 1024
alloc'd
==25618== at 0x4004749B: malloc
(/tmp/buildd/valgrind-1.0.3/vg_clientfuncs.c:100)
==25618== by 0x40652410: (within /usr/X11R6/lib/libICE.so.6.3)
==25618== by 0x40648301: (within /usr/X11R6/lib/libSM.so.6.0)
==25618== by 0x404ECC77: (within /usr/lib/libgnomeui.so.32.14.1)
VG_(get_memory_from_mmap): request for 1953656832 bytes failed.
VG_(get_memory_from_mmap): 58853360 bytes already allocated.
This may mean that you have run out of swap space,
since running programs on valgrind increases their memory
usage at least 3 times. You might want to use 'top'
to determine whether you really have run out of swap.
If so, you may be able to work around it by adding a
temporary swap file -- this is easier than finding a
new swap partition. Go ask your sysadmin(s) [politely!]
VG_(get_memory_from_mmap): out of memory! Fatal! Bye!
total used free shared buffers cached
Mem: 255892 220004 35888 0 22864 87660
-/+ buffers/cache: 109480 146412
Swap: 491360 190240 301120
If it really requires over 300 Meg of memory to use to debug Gnome
programs, that sort of puts me off it just a tad...
Running top at the same time, I see the free memory dropped to about 9Meg, but
swap isn't affected. This might just be a matter of poor timing though.
--
Brian May <bam@debian.org>
Reply to: