PRB: WinDbg Gets Stuck in a Hard-coded Breakpoint

• Microsoft Win32 Device Driver Kit (DDK) for Windows NT, versions 3.51, 4.0

SYMPTOMS

When trying to debug a Windows NT driver using WinDbg in the SDK, you often stopped in the Command Window with the following debug message:

Hard coded breakpoint hit

RESOLUTION

Pressing the F5 key (Go) does not let you past the breakpoint. You must first press the F8 key (Trace Into) to bypass the hard-coded breakpoint.

STATUS

This behavior is by design.

Additional query words: 3.51 4.00

Keywords : NTDDKDebug NTDDKKMode
Version : 3.51 4.00
Platform : NT WINDOWS
Issue type :