On Sat, May 21, 2011 at 12:27 AM, Eric Schwarz wrote:
>
> Is this a known behaviour for vector<>'s standard allocator to allocate and
> hand back like this?
>
> Does anyone know why this is the case? - Sorry for might posting C++ related
> question.
A C++ vector implementation might do all sorts
Hi all
I have profiled two source code examples [1], [2] using Valgrind's massif.
The following command has been used
# valgrind --tool=massif --time-unit=B --stacks=yes
--massif-out-file=.massif.out ./
The output file has been printed w/ ms_print.
[3] is the print for [1] .
[4] is the prin
