Tuesday, September 29, 2009
Using umdh to trace down Windows memory leaks
- Install Windbg
- set path="C:\Program Files\Debugging Tools for Windows (x64)";%path%
- enable sysmtem stack trace - gflags -r +ust
- md c:\websymbols
- set symbols path - set _NT_SYMBOL_PATH=SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;X:\Symbols\exe64ex
- snap process memory - umdh -p:pid -f:output-1-file
- snap process memory again - umdh -p:pid -f:output-2-file
- compare two memory snap - umdh output-1-file output-2-file -f:cmp.txt
- cmp.txt should contain leak information.
# posted by James Tatum @ 10:12 AM 
