|
From: Shehjar T. <she...@cs...> - 2008-01-21 03:58:44
|
Hi All I am running massif for a program that does quite a lot of memory allocation, to profile the heap usage. The problem is, at the end of the run, massif does not create the postscript file with the heap usage plot in it. I've used massif before on the same setup which correctly generated the postscript file but that was a few months back and the same setup does not generate the PS file as expected now. I could not find anything about this problem in the list archives so decided to post here. The details are: valgrind-3.3.0 Linux kernel 2.6.24-rc7 with gcc version 4.2.3 20071123 on Debian 4.2.2-4 Machine is an AMD64 SMP. Target executable is built with ggdb3 argument to gcc. The valgrind massif output is here: http://www.gelato.unsw.edu.au/~shehjart/download/vgrind.txt and the one text file that does get generated is here: http://www.gelato.unsw.edu.au/~shehjart/download/massif.out.15194.txt but I have no idea what this file is supposed to be used for. Note that the output in the above files contains a program run which I interrupted before completion to get just enough info for this post. I can provide more information, if needed. Thanks Shehjar |
|
From: Nicholas N. <nj...@cs...> - 2008-01-21 10:27:49
|
On Mon, 21 Jan 2008, Shehjar Tikoo wrote: > I am running massif for a program that does quite a lot of memory > allocation, to profile the heap usage. The problem is, at the end of > the run, massif does not create the postscript file with the heap > usage plot in it. In version 3.3.0, Massif was changed somewhat. From the release notes: - Massif has been completely overhauled. Instead of measuring space-time usage -- which wasn't always useful and many people found confusing -- it now measures space usage at various points in the execution, including the point of peak memory allocation. Its output format has also changed: instead of producing PostScript graphs and HTML text, it produces a single text output (via the new 'ms_print' script) that contains both a graph and the old textual information, but in a more compact and readable form. Finally, the new version should be more reliable than the old one, as it has been tested more thoroughly. So the behaviour you're seeing is as expected. Nick |