Hello folks,
we run a database on valgrind and tests on that database, to find memory leaks. 
The tests are written in Python, the database is written in C++. A test 
contains many testcases and configurations, so that a test may run more than 12 
hours and has all in all (with all combinations of testcases and 
configurations) more than 10000 testruns (i.e. a testrun is a combination of a 
testcase with a configuration). If a memory leak was detected, it was helpful, 
to know, to which testrun this leak belongs.

The testrun-name itself is not printed out in the stack (because the stack only 
contains the C++-stack - of course - and the testrun-name is visible in Python, 
only), therefore, we need to map the time, when the test was started and the 
time, when the memory leak occurred. We use the time-stamp parameter, to detect 
the latter. The timestamp printed out by valgrind is now not the timestamp of 
allocation, but of 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 
that a match between testrun and memory leak is impossible. Now I would like to 
modify the sources of valgrind, so that the time of allocation is also stored 
internally and printed out in the summary.

Could you please kindly give me a hint, which structure was to change and where 
there timestamp then needs to be inserted?

I am fine with the relative time-stamp; I do not need an absolute one!

Kind regards and thank you,

Robin Rehrmann



------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to