Debugging GP Faults with WDEB386

 Last reviewed: August 12, 1997
Article ID: Q77987

The information in this article applies to:

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

Under certain circumstances, trying to trap GP (general protection) faults with WDEB386 may produce unexpected results.

In general, if the processor generates a GP fault while a Windows-based application is running, the GP-fault handler will automatically provide the mechanism to stop at the offending instruction in WDEB386. However, unexpected results (breaking at unusual locations, infinite loops, debugger crashes) may occur under WDEB386 if one of the following conditions is true:

- The GP fault occurs somewhere other than in a Windows-based application 

  or dynamic-link library (DLL).
- The WIN.INI file [kernel] section switch DisableGPTrapping is set to 
  1.


Keywords          : kb16bitonly TlsWdeb kbtool
Version           : 3.0 3.1
Platform          : WINDOWS
Issue type        : kbhowto

================================================================================

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