Viewing the debug logs of MEMORY.DMP in Debugview

WINDBG
1

Hi,

I am trying to analyze a crash dump.
Is it possible to view the log prints from MEMORY.DMP file using Debugview tool?
Could you please let me know where I can find information on this.
Currently I am not able to view the log prints when I open the MEMORY.DMP file in Debugview tool.

Thanks,
Vinayak

2

The O/S does buffer *some* trace messages in some cases, you can see if
they’re still there with !dbgprint. If you don’t get any results then you’re
out of luck. If you do get results, note that the traces are kept in a ring
buffer and !dbgprint doesn’t take into account the head and tail pointers.
Thus, the trace messages that you see were not necessarily displayed in that
order.

Of course, if you hook WinDbg up to the machine and reproduce the problem
you can get the traces directly from the Command Window.

-scott
@OSRDrivers

wrote in message news:xxxxx@windbg…

Hi,

I am trying to analyze a crash dump.
Is it possible to view the log prints from MEMORY.DMP file using Debugview
tool?
Could you please let me know where I can find information on this.
Currently I am not able to view the log prints when I open the MEMORY.DMP
file in Debugview tool.

Thanks,
Vinayak

3

Scott Noone wrote:

The O/S does buffer *some* trace messages in some cases, you can see if
they’re still there with !dbgprint. If you don’t get any results then you’re
out of luck.

Maybe it is the result of a sinful life, but I have NEVER seen the
!dbgprint command produce a non-null result.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

4

DbgPrints must already be enabled via the registry (and the global
“nt!kd_xxx_mask” variable must still be set). Just ran it against my 8.1
target:

0: kd> !dbgprint
nh.exe" found in cache
Application “??\C:\Windows\system32\taskhost.exe” found in cache
Application “??\C:\Windows\Explorer.EXE” found in cache
SHIMVIEW: ShimInfo(Complete)
…

There is always time to repent!

-scott
@OSRDrivers

“Tim Roberts” wrote in message news:xxxxx@windbg…

Scott Noone wrote:

The O/S does buffer *some* trace messages in some cases, you can see if
they’re still there with !dbgprint. If you don’t get any results then
you’re
out of luck.

Maybe it is the result of a sinful life, but I have NEVER seen the
!dbgprint command produce a non-null result.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.