PRB: WinDbg Gets Stuck in a Hard-coded Breakpoint

Last reviewed: April 7, 1997
Article ID: Q151330

3.51 4.00 WINDOWS NT kbprg kbprb

The information in this article applies to:

Microsoft Win32 Device Development 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 reference words: 3.51 4.00
KBCategory: kbprg kbprb
KBSubcategory:
Keywords : NTDDKDebug NTDDKKMode kbprb kbprg
Version : 3.51 4.00
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.