PRB: WinDbg Gets Stuck in a Hard-coded Breakpoint

Q151330

The information in this article applies to:

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
Issue type :
Technology :


Last Reviewed: December 9, 1999
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.