Quantcast
Channel: Visual Leak Detector for Visual C++ 2008-2015
Viewing all articles
Browse latest Browse all 704

New Comment on "Using Visual Leak Detector"

$
0
0
On further use, I noticed that the summary total of the number of bytes leaked reported by VLD does not agree with the sum of the reported leaked bytes. The summary number of leaks does agree. I tested this using the following options: [Options] VLD = on AggregateDuplicates = no ForceIncludeModules = MaxDataDump = 32 MaxTraceFrames = ReportEncoding = ascii ReportFile = W:\Main\EnsorApplication\Castor\Build\VC90NT\Castor\Win32\Debug\vld_leak_report.txt ReportTo = file SelfTest = off StackWalkMethod = fast StartDisabled = no TraceInternalFrames = no SkipHeapFreeLeaks = no At the end of the generated report: Visual Leak Detector detected 11470 memory leaks (774260 bytes). When I use scripts to calculate these figures for myself cat /cygdrive/c/Users/21ppm/Desktop/vld_leak_report.txt | grep "\-\- Block" | wc -l 11470 (correct) cat /cygdrive/c/Users/21ppm/Desktop/vld_leak_report.txt | grep "\-\- Block" | cut -f2 -d':' | cut -f2 -d' ' | awk 'a+=$1; END{print a}' 361340 (reported total was 774260)

Viewing all articles
Browse latest Browse all 704

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>