Hello John.
I already went over the manual, and did not find anything that helped including
the --freelist-* flags.
I found answers for all of your questions below, but they are not relevant any
more.
Following your advice to construct the smallest stand-alone test case,
I saw that the problem
I already went over the manual, and did not find anything that helped
including the --freelist-* flags.
Please read more carefully. I found relevant material which I pinpoint below
in the hope that specific references may help increase understanding for future
uses.
I downloaded the manual
On Thu, 2013-03-14 at 13:47 -0700, John Reiser wrote:
In the NEWS section, Release 3.8.0 (10 August 2012), TOOL CHANGES,
* Non-libc malloc implementations are now supported. This is useful
for tools that replace malloc (Memcheck, Massif, DRD, Helgrind).
Using the new option
Hello all.
I am trying to find memory corruption using valgrind/memcheck.
I am running a big executable, and noticed that memory access outside allocated
areas is not detected. This happens after very many memory allocations are
performed.
I am testing access to illegal memory and finding that
I am trying to find memory corruption using valgrind/memcheck.
I am running a big executable, and noticed that memory access outside
allocated areas is not detected. This happens after very many memory
allocations are performed.
How big (numbers, please)? Run /usr/bin/top and report the
