PRB: Encountering an INT 01 with WDEB386

Last reviewed: July 22, 1997
Article ID: Q64123

3.00 3.10 WINDOWS kbprg kbprb

The information in this article applies to:

Microsoft Windows Software Development Kit (SDK) for Windows versions 3.0 and 3.1

SYMPTOMS

When debugging an application with WDEB386, the program halts on a breakpoint at an INT 01 instruction.

CAUSE

An INT 01 is coded into Windows in the Fatal_Error_Handler. This interrupt is hit when some device driver is doing a fatal exit. The INT 01 is there to make the debugger useful when diagnosing the fatal error. INT 01 in virtual devices (VxDs) is generally ignored (treated as a NOP instruction) in the retail version of Windows. However, if the debugger is installed, the system breaks into the debugger.

RESOLUTION

Diagnose and correct the cause of the fatal exit.

Additional reference words: 3.00 3.10
KBCategory: kbprg kbprb
KBSubcategory: TlsWdeb
Keywords : kb16bitonly

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: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.