INFO: Choosing the Debugger That the System Will Spawn

 Last reviewed: May 27, 1997
Article ID: Q103861

The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) versions 3.1, 3.5, 3.51, 4.0

SUMMARY

It is possible to have the system spawn a debugger whenever an application faults. The capability is controlled by the following Registry key on Windows NT: 

   HKEY_LOCAL_MACHINE\
             SOFTWARE\
            Microsoft\
           Windows NT\
       CurrentVersion\
              AeDebug
This key contains the following entries: 

   Auto
   Debugger
These entries are also available on Windows 95. However, on Windows 95, they are contained in the win.ini file instead of the registry. The section [aedebug] has entries that correspond to the registry.

If the value of Auto is set to "0" (zero), then the system will generate a pop-up window, and if the user chooses Cancel, spawn the debugger that is specified in the Debugger value. If the value of Auto is set to "1", then the system will automatically spawn the debugger that is specified in the Debugger value.

After installing Windows NT, the Debugger value is set to 

   DRWTSN32 -p %ld -e %ld -g
and the Auto value is set to 1. If the Win32 SDK is installed, then the Debugger value is changed to 

   <MSTOOLS>\BIN\WINDBG -p %ld -e %ld
and the Auto value is set to 0.

Microsoft Visual C++ version 5.0 makes the following entry for the Debugger value: 

   C:\Program Files\DevStudio\SharedIDE\BIN\msdev.exe -p %ld -e %ld

MORE INFORMATION

The DRWTSN32 debugger is a post-mortem debugger similar in functionality to the Windows 3.1 Dr. Watson program. DRWTSN32 generates a log file containing fault information about the offending application. The following data is generated in the DRWTSN32.LOG file:

  • Exception information (exception number and name)
  • System information (machine name, user name, OS version, and so forth
  • Task list
  • State dump for each thread (register dump, disassembly, stack walk, symbol table)

A record of each application error is recorded in the application event log. The application error data for each crash is stored in a log file named DRWTSN32.LOG, which by default is placed in your Windows directory.

Keywords : kbtool TlsMisc
Version : 3.1 3.5 3.51 4.0
Platform : NT WINDOWS
Issue type : kbinfo

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