I've used UMDH a dozen times before, never with any problem. Suddenly I don't get a function names in the stack traces in my dump files - just a series of addresses. I've got ust enabled: gflags exe_name +ust I start exe_name, then I do umdh -p:pid one.txt umdh -p:pid two.txt I look at one.txt and two.txt and they have no indicat...
Hi All, Am using umdh.exe to analyze possible memory leak. I have a question regarding the '-g' option of umdh.exe. I searched the web, and the available documentation says "Logs the heap blocks that are not referenced by the process ("garbage collection")." Does that mean umdh.exe -g already lists the memory that has leaked (since the...
Usually, when tracking down a memory leak in a Visual C++ program, I recompile to make use of all of the good stuff in <crtdbg.h>. Last week, however, I stumbled across UMDH, part of the Debugging Tools for Windows. It can take before/after snapshots of memory usage, and then compare them, allowing you to find your leaks. I assume that...
I am new to using UMDH, and I am having some trouble understanding how to proceed with some of the errors it is outputting. I follow the typical usage (from the MS site): gflags -i OCES.exe +ust In another terminal window: OCES.exe And then back in the original terminal window: umdh -p:5712 -f:out1.txt But I am getting the follo...