When I try to get allocation stack traces with !heap -p -a <address of allocated memory> while user stack tracing is active (gflags.exe /i program.exe +ust) then in the old WinDbg 10.0.19041.685 I get the expected result.
In the new WinDbg version 1.2303.30001.0 I just get
**********************************************
The `!heap -p' commands in exts.dll have been replaced
with equivalent commands in ext.dll.
If you are in a KD session, use `!ext.heap -p`
**********************************************
and !ext.heap -p -a <address of allocated memory> doesn't show any output.
When I try to get allocation stack traces with
!heap -p -a <address of allocated memory>
while user stack tracing is active (gflags.exe /i program.exe +ust
) then in the old WinDbg 10.0.19041.685 I get the expected result.In the new WinDbg version 1.2303.30001.0 I just get
and
!ext.heap -p -a <address of allocated memory>
doesn't show any output.Is it broken, or am I doing something wrong?