On Mon, 23 Jan 2012 11:20:20 +0100, Julian Seward wrote:
> You
need to figure out whether the extreme growth is due to the
> behaviour
of your program, or a bug in Valgrind. You can investigate
> the space
usage of your program in various ways (some of which
> PhilippeW has
already described) and you can also use the tools
> --tool=massif and
(advanced, but sometimes interesting) --tool=exp-dhat.
>
> If you
program is multithreaded you might also want to consider
> if there are
any threading errors that could account for the
> possibly inconsistent
behaviour.
>
> J
Thanx Julian. I have no problems in my program when
NOT running with valgrind, but I fully understand that this is NOT a
proof for not having a bug.
I will surely follow the good hints from
PhilippeW.
I did try massif, but the program is terminated (3G limit)
before I get any output. It seems to happen extremely fast.
I do have
3 threads, so your idea about exp-dhat is the next thing I will try.
Thanx
--
Peter Toft, PhD
http://petertoft.dk
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
