PRB: Just-In-Time Debugging Launches Wrong Debugger

Last reviewed: July 24, 1997
Article ID: Q138786
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 5.0

SYMPTOMS

Although Just-In-Time (JIT) debugging is enabled in the Developer Studio, a debugging utility other than the Developer Studio is invoked when an illegal operation occurs in Windows 95.

CAUSE

In Windows 95, the Developer Studio uses the Win.ini file to maintain the just-in-time debugging settings. If the following registry key exists in your Windows 95 registry, its settings will preempt the settings in the Win.ini file:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\AeDebug

RESOLUTION

Delete the following registry entry to allow Visual C++ just-in-time debugging to be invoked:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\AeDebug

STATUS

This behavior is by design.

MORE INFORMATION

In Windows NT, this information is kept only in the registry.

In Windows 95, it is necessary for this information to be placed in the Win.ini file only. Installing the Win32 SDK on a computer that is running Windows 95 will create a registry key and cause the problem described. Use Regedit.exe to delete the key from the registry.

The following entries should exist in the Win.ini file:

   [AeDebug]
   Auto=0
   Debugger=c:\msdev\bin\msdev.exe -p %ld -e %ld

The path to Msdev.exe may be different on your computer. The Win.ini file is located in your Windows directory.

REFERENCES

The Readme for Microsoft Visual C++ Version 4.0.


Keywords : kbtshoot WBDebug
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbprb


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