Re: [DUnit-interest] Re: Adding Memory leak detection per test.

[Peter M. <mc...@me...>]

Kristofer G. Skaug [home] wrote:

> Peter McNab wrote:
>
>> If committers consider leak detection a worthwile addition for future
>> releases of DUnit then I will post a patch.
>
>
> Hi Peter,
>
> sounds interesting, although since I started using FastMM4 I get 
> automatic leak reporting in my apps, so I don't miss it as much as 
> before.
> Could you tell us more about your approach?
>
> Does it require inserting calls (e.g. StartLeakMonitor/EndLeakMonitor 
> - modelled after the "Expected exceptions" mechanism) or is it always 
> on (with no mods to existing test code)? Does it involve using a 
> specific replacement memory manager? etc.
> Might be useful to share this so you can have early feedback ...
>
It makes use of unmodified FastMM4 and surrounds each test with memory 
status calls with a before after check.
The code had been implemented so Checkxxx() failures trump memory leak 
reporting.
Currently there is no atttempt to identify the precise code which 
generated the leak as I believe MemProof is better suited to that purpose.

Peter