Hi,
I recently had to debug a double free. This could have been a piece of cake
with Valgrind, but unfortunately the first and second frees were a few minutes
of runtime apart, so all I got was the "address was not recently malloc()ed..."
message instead of the backtrace corresponding to the first free.
When I increased the -free-list-vol to the maximum value allowed by Valgrind,
Valgrind aborted prematurely, apparently because the 32G memory limit was
reached. My machine had 96G, and I'm sure it would have been enough for
obtaining the backtrace of the first free.
Is it possible to overcome the 32G limit? I don't think machines with more
memory than that are rare.
Thanks,
Meir
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
