What causes UMDH not to produce stack traces

Question

I used UMDH a dozen times before, never with any problem.

Suddenly, I don't get the function names in the stack trace in the dump files - just a few addresses.

I have ust enabled:

gflags exe_name + ust

I run exe_name, then I do

umdh -p: pid one.txt umdh -p: pid two.txt

I look at the files one.txt and two.txt and they have no indication of where they come from. When i do diff

umdh one.txt two.txt> diff.txt

the result is not useful.

Help, I like this tool.

Answer 1

UMDH executes the PDB command when executing the command:

umdh -d one.txt two.txt -f: outputfile.txt

. diff !

, ... .

Answer 2

UMDH - -tools-for-windows. , . -

umdh -p: pid ** - f: ** one.txt

umdh -p: pid ** - f: ** two.txt

umdh -v -l one.txt two.txt > diff.txt

(- l - , PDB). , _NT_SYMBOL_PATH PDB.

.

(:) , -v, ...

(EDIT:) . , VC8, CRT malloc FPO - UMDH . , (. ), UMDH , . SysAllocString. , LeakDiag - .

Answer 3

PDB.

, ,
UMDH , , .