[Valgrind-users] massif: accurate peak memory usage?

Can Massif give an accurate value for peak memory usage, without running very slowly? I understand that recording a detailed snapshot is expensive, hence the --peak-inaccuracy option. But in my case, I'm not interested in a detailed snapshot; all I want is an accurate value for the peak memory

Re: [Valgrind-users] full path to source

Thanks Bart but I'm using valgrind 3.5.0 and I don't see it -Original Message- From: bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] On Behalf Of Bart Van Assche Sent: Friday, March 18, 2011 4:14 AM To: Osman, Ahmed Cc: valgrind-users@lists.sourceforge.net Subject: Re:

Re: [Valgrind-users] full path to source

Hello Ahmed, It's pretty easy to download the 3.6.1 source code from www.valgrind.org and to compile and install it. Any software developer should be able to do that. Bart. On Mon, Mar 21, 2011 at 7:11 PM, Osman, Ahmed ahmed_os...@mentor.com wrote: Thanks Bart but I'm using valgrind 3.5.0 and

[Valgrind-users] Is there a way to clear helgrind's lock ordering graph?

Hi, I am using helgrind to look for deadlocks in a C++ server program. I am running into the following problem: There are some objects that are declared statically in the server. I am seeing stack traces for Required order that include __static_initialization_and_destruction_0(...) in the