
15 Jun
2008
15 Jun
'08
9:15 p.m.
Mike(dev
When trying to determine where memory leaks are coming from, you could try something like this...
#include
int main() // try replacing this line with BOOST_AUTO_TEST_CASE_TEMPLATE { // break on memory allocation number _crtBreakAlloc = 83; // or 84, 93,94 }
Boost.Test supports this directly just pass allocation number as the value of the argument detect_memory_leaks: test_modul.exe --detect_memory_leaks=83 Unfortunately in my experience with previous version of MS runtime this doesn't actually break exactly at the same allocation we if you did not pass the parameter. It's somewhere in a vicinity though: plus/minus couple. Gennadiy