On Tue, 2012-11-27 at 23:35 +0100, Philippe Waroquiers wrote:
On Mon, 2012-11-26 at 12:46 -0800, Wiser, Tyson wrote:
Does anyone have any idea what I am doing wrong? I am new to valgrind
so I'm sure it is something simple that I have missed.
I just saw your follow-up telling you have a
From Valgrind 3.8.1 onwards, Valgrind can properly work with
statically linked malloc libraries thanks to the option
--soname-synonyms=somalloc=NONE
This option can also be used to support alternative malloc libraries
such as tcmalloc. See user manual for details.
I will update Valgrind FAQ
On Wed, 2012-11-28 at 11:06 -0800, Wiser, Tyson wrote:
I tried it with 3.8.1 that I built locally and got the same result
(i.e. no profile). The command I used was:
valgrind --tool=massif --soname-synonyms=somalloc=NONE ./MyProg
The above is supposed to properly replace a static malloc.
I
Currently, Valgrind does not provide a fully flexible
way to indicate which leak kinds to show,
which leak kinds to consider as an error,
and which leak kinds to suppress.
This is a.o. described in bugs 284540 and 307465.
For example, the current options
(--show-reachable=yes|no
hi :
When I do some operation(open many threads and exit these threads) in my
program, memory used increase, when I exit my program, valgrind tell me there
is no memory leak.What I expect is after open many threads and exit these
threads, the memory used is keep same as before.How can I
The pattern
6cf7a000 4 - 000:0 [ anon ]
6cf7b0008192 rw--- 000:0 [ anon ]
with one 4KiB page of no access (-) adjacent to 8MiB of rw---
is [or perhaps, was] the default-sized stack of a thread. When a
thread terminates, then glibc
On Wednesday 28 November 2012 23:56:55 Philippe Waroquiers wrote:
Currently, Valgrind does not provide a fully flexible
way to indicate which leak kinds to show,
which leak kinds to consider as an error,
and which leak kinds to suppress.
This is a.o. described in bugs 284540 and 307465.
