On 11/28/2012 02:56 PM, Philippe Waroquiers wrote:
Currently, Valgrind does not provide a fully flexible
way to indicate which leak kinds to show,
which leak kinds to consider as an error,
and which leak kinds to suppress.
This is a.o. described in bugs 284540 and 307465.
Here are the new
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
Hi
I work with a software that uses boost memory mapping and seems that I
can't run it inside massif nor memcheck, the error is:
(boost::interprocess::mapped_region::mapped_regionboost::interprocess::file_mapping(boost::interprocess::file_mapping
const, boost::interprocess::mode_t, long,
On Thu, 2012-11-29 at 08:44 +0100, David Faure wrote:
Here are the new command lines args:
--show-leak-kinds=kind1,kind2,.. which leak kinds to show?
[definite,possible]
--errors-for-leak-kinds=kind1,kind2,.. which leak kinds are
On Thu, 2012-11-29 at 06:25 -0800, John Reiser wrote:
This is good as far as it goes. The presentation in the output from
valgrind --help will matter, and so will the explanation given
in the user manual. Just finding and understanding the new options
is a significant barrier to usability.
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 Thu, 2012-11-29 at 17:31 +0100, Pedro Larroy wrote:
Without valgrind everything works fine, it tries to map a file of 20GB
or so, might this be the reason?
Yes, it might be the reason.
Try to reduce the size to e.g. 1GB and see if it works.
-v -v -v -d -d -d args will also activate tracing
