Never mind, I found the problem. I'll be submitting a (tested and working) patch soon. Turns out, I have to let the destructor call for the fixtures before checking for memory leaks, or else STL will still be storing things in strings/vectors. That was fun.
On 20/01/2010 2:52 PM, Clark Gaebel wrote: > Attached is a patch to enable memory leak detection (sorry for breaking > your build, Alex). There's a little problem though. It works perfectly > for all my tests, but fails with the bootstrap. Only the deferred/xml > test reporter tests trigger it. So is this a legitimate memory leak, or > is my method interfering with their operation? Is it a problem with > fixtures? > > NOTE: In order to use this, you'll probably need to add LeakDetector.cpp > and LeakDetector.h to your project. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
