To see that the whole replacement thing is working,
the command
valgrind --tool=memcheck --soname-synonyms=somalloc=NONE ./static_malloc
should produce lines telling that the heap was used e.g.
==14445== total heap usage: 2 allocs, 1 frees, 133 bytes allocated
...
==14445==
On Fri, 2012-11-30 at 06:56 -0800, Wiser, Tyson wrote:
I'm not sure how to interpret these results. Does all this look OK?
Yes, it looks similar to what I see here.
To see that the whole replacement thing is working,
the command
valgrind --tool=memcheck --soname-synonyms=somalloc=NONE
Can you try with -v and/or with --trace-redir=yes ?
That might give some lights about the problem ?
I used both options and it produced the following output. Thanks for taking
the time to look at this.
==9674== Massif, a heap profiler
==9673== Copyright (C) 2003-2012, and GNU GPL'd, by
On Thu, 2012-11-29 at 07:30 -0800, Wiser, Tyson wrote:
Can you try with -v and/or with --trace-redir=yes ?
That might give some lights about the problem ?
I used both options and it produced the following output. Thanks for taking
the time to look at this.
There is an unexpected (or rather
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
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.
Not too sure it is very simple. Normally, massif should work with default args.
Maybe there is a problem with
I am developing a 64-bit C++ application on 64-bit CentOS 5.8 using the
standard CentOS packages (gcc 4.4.6, not 4.1.2). It has been compiled with
debug information. When I try profiling it with massif I always get the
following in the massif.out. file using the command 'valgrind
