Hi Robin,
Thank you for your answer. Instead of using a timestamp to compare logs, I
put a client request (VALGRIND_DO_LEAK_CHECK or
VALGRIND_DO_CHANGED_LEAK_CHECK) in my code as Philippe suggested, so I can
run the test and then call the leak check.
Best Regards,
Willian
Thank you,
that fixed it!
Robin
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
Presumably what you want is to track the systime of an allocation as part of
the allocated chunk later to be retrieved during leak_check(), and print
it?.
The structure MC_Chunk in memcheck/mc_include.h is (I think) allocated
every time a malloc-like call is replaced by MC_(new_block). You could
On Mon, 2013-02-04 at 16:26 +, Rehrmann, Robin wrote:
printing the result. Since memory leaks can only be detected at the
end of a program, these are printed out at the end of the program, so
If you want to find which test specifically leaks some memory
(i.e. loses the last pointer to a
