The example program is run once and we use the Memory view to observe and investigate any double deallocations.
For each double deallocation, Memory Validator displays the allocation and deallocation locations.
launch nativeExample.exe wait until attaching is complete
Memory Errors menu Incorrect Usage Double Delete forces a double deallocation in the example application
If a heap warning dialog appears, choose Ignore to continue.
File menu Exit
wait for data transfer to complete
•Memory tab Refresh shows the usual leaks and also multiple deallocations using the colour defined.
•expand the most recent double deallocation shows the locations for allocation, free and double free
•expand the topmost entries in each callstack shows the successive lines of the test in CTeststakView::OnTestDoubledeleteofmemory()