Breaking on crash in windbg

NTDEV
1

I have windbg talking to Win7 in Virtual PC via a named pipe to a COM,
and my driver is causing the VM to spontaneously reset. Is it possible
to have windbg break into the kernel once at the time/location of the
fault so that I can inspect what happened? Are there any other
tools/techniques that could help me figure out what’s going on,
besides iterating the code with guess-and-check changes? Thanks.

Yang Zhang
http://www.mit.edu/~y_z/

2

If you have the debugger setup properly, then you are probably causing a triple fault.

The short answer is: That’s a pain to debug.

Likely the fastest approach is to backtrack until you aren’t doing this anymore, and/or code review your recent changes.

  • S

-----Original Message-----
From: Yang Zhang
Sent: Wednesday, September 30, 2009 18:29
To: Windows System Software Devs Interest List
Subject: [ntdev] Breaking on crash in windbg

I have windbg talking to Win7 in Virtual PC via a named pipe to a COM,
and my driver is causing the VM to spontaneously reset. Is it possible
to have windbg break into the kernel once at the time/location of the
fault so that I can inspect what happened? Are there any other
tools/techniques that could help me figure out what’s going on,
besides iterating the code with guess-and-check changes? Thanks.
–
Yang Zhang
http://www.mit.edu/~y_z/

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer