Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Difference between revisions of "Microsoft KB Archive/172779"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 32: Line 32:
 
There are several causes for this type of behavior.<br />
 
There are several causes for this type of behavior.<br />
 
<br />
 
<br />
The first cause of this symptom could be that the application crashed. When an application &quot;crashes&quot; in Windows NT, NT will attempt to load a specified debugger to log information about the crash. By default, Windows NT launches Dr. Watson to capture such crashes.<br />
+
The first cause of this symptom could be that the application crashed. When an application "crashes" in Windows NT, NT will attempt to load a specified debugger to log information about the crash. By default, Windows NT launches Dr. Watson to capture such crashes.<br />
 
<br />
 
<br />
If the default debugger is removed or no debugger is specified, the system will attempt to launch the debugger, but since the debugger is no longer installed or specified, the debug launch will just quit, and the crashing application will die/&quot;disappear&quot; with no warning notice.
+
If the default debugger is removed or no debugger is specified, the system will attempt to launch the debugger, but since the debugger is no longer installed or specified, the debug launch will just quit, and the crashing application will die/"disappear" with no warning notice.
  
 
<br />
 
<br />

Latest revision as of 11:06, 21 July 2020

No Default Debugger Causes Application to Close Without Warning

Q172779



The information in this article applies to:


  • Microsoft Windows NT Workstation versions 3.51, 4.0
  • Microsoft Windows NT Server versions 3.51, 4.0





SYMPTOMS

Applications that are running on Windows NT Server or Windows NT Workstation, either 16 bit or 32 bit, mysteriously close with no warning.



CAUSE

There are several causes for this type of behavior.

The first cause of this symptom could be that the application crashed. When an application "crashes" in Windows NT, NT will attempt to load a specified debugger to log information about the crash. By default, Windows NT launches Dr. Watson to capture such crashes.

If the default debugger is removed or no debugger is specified, the system will attempt to launch the debugger, but since the debugger is no longer installed or specified, the debug launch will just quit, and the crashing application will die/"disappear" with no warning notice.



WORKAROUND

To ensure that you are using the correct debugger, check the following registry key:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Start Registry Editor and locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:

          \Software\Microsoft\Windows NT\CurrentVersion\AEDEBUG 
  2. For more information on this setting, see the following article in the Microsoft Knowledge Base:

Additional query words: debugref

Keywords :
Issue type : kbprb
Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT351xsearch kbWinNT400xsearch kbWinNTW351xsearch kbWinNTW351 kbWinNTSsearch kbWinNTS400xsearch kbWinNTS400 kbWinNTS351 kbWinNTS351xsearch


Last Reviewed: February 27, 1999
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.