Monitoring ADPlus in Crash Mode

To determine where ADPlus has captured information about a failure (that is, crash) or if a process that is being monitored in crash mode has shut down, you can do the following:

• Use the -notify option, and make sure that the messenger service is started on the server that is being debugged and on the client computer that receives notifications.
• In the output directory, open the .log file for each process in a text editor, and scroll to the end of the file. Look for the following text:

  0:070> * -------- AutodumpPlus 4.01 finished running at: --------
  0:070> .time
  Debug session time: Mon Aug 06 15:25:15 2001
  System Uptime: 3 days 17:00:34 
  Process Uptime: 1 days 3:10:38 
  0:070> * ------------------------------------------------------- 
  

• In the output directory, look for any .dmp files that contain the phrase "__2nd_chance". If a memory dump is labeled with this phrase, a process has failed.
• In the output directory, look for any .dmp files that contain the phrase "__Process_was_shutdown". If a memory dump is labeled with this phrase, an administrator ended the process or, if the process is an MTS or COM+ application, it might have been shut down because the idle limit was reached.
• In the output directory, look for any .dmp files that contain the phrase "__CTRL-C". If a memory dump is labeled with this phrase, a debug break exception was thrown from a DLL that was running inside the process or someone pressed CTRL+C from the console (or used Breakin.exe if running remotely) to stop the current debugging session.