Incorrect Time-Stamps In Valgrind Memory Leak Report

Question

I am running Valgrind over a large code-base, with "--time-stamp=yes"

I need to find out the ACTUAL (Relative) TIMESTAMPS at which each Memory was Allocated

Problem: Valgrind Report contains the Time-Stamps at which Leak Summary is generated

Steps:

 - Run the codebase for 24 Hours with valgrind [ options
   "--tool=memcheck --leak-check=full --time-stamp=yes"]


 - Terminate the process with "kill -15" after 24 hours, Leak Summary is
   generated.


 - Time-Stamps In Valgrind Report= Time of Leak Report Generation [Not
   the Actual Time at which Memory was Allocated]

Is there any option thorough which I can get the ACTUAL TIMESTAMPS -- at which Leaked Memory was Allocated ?

Thanks

Answer 1

No, there isn't, because leaks are not detected in real time - there isn't really any way to do that. Instead they are detected by scanning memory when the program finishes, to see what blocks are still reachable - anything which has been allocated but is not reachable is a leak.