|
From: Tom H. <to...@co...> - 2005-03-18 16:35:47
|
In message <423...@la...>
Boris Mansencal <bor...@la...> wrote:
> I am using current Valgrind version from CVS (on a Fedora Core 1 or 3
> system, Intel P4).
>
> Valgrind with Memcheck (or Addrcheck or even Massif) does not see any
> of my memory allocation !
> It always reports :
> ==11522== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
> ==11522== malloc/free: in use at exit: 0 bytes in 0 blocks.
> ==11522== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
> ==11522== For counts of detected errors, rerun with: -v
> ==11522== No malloc'd blocks -- no leaks are possible.
Is your program statically linked? If it is then valgrind won't be
able to see any of the calls to malloc/free etc.
> ==23355== Contents of /proc/version:
> ==23355== Linux version 2.6.9-1.667
> (bhc...@tw...) (gcc version 3.4.2 20041017 (Red
> Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:25 EST 2004
> ==23355== census: 0 ms (took 0 ms)
> ==23355== Reading syms from
> /net/tera4/mansenca/toger/girl/src/test-toger (0x8048000)
> ==23355== object doesn't have a dynamic symbol table
> ==23355== Reading syms from
> /net/tera4/mansenca/tools/lib/valgrind/stage2 (0xF0000000)
> ==23355== Reading syms from /lib/ld-2.3.3.so (0xF1000000)
> ==23355== object doesn't have any debug info
> ==23355== Reading syms from
> /net/tera4/mansenca/tools/lib/valgrind/vgskin_massif.so (0xF6DB0000)
> ==23355== Reading syms from /lib/tls/libc-2.3.3.so (0xF6EC1000)
> ==23355== object doesn't have any debug info
> ==23355== Reading syms from /lib/libdl-2.3.3.so (0xF6FE9000)
> ==23355== object doesn't have any debug info
> ==23355==
There's no obvious sign of it reading symbols for libc there, although
it might be in the bit you snipped. That might suggest a static link.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|