drwatson

We used to use Dr. Watson logfiles and dumps for crash analysis in our production environment, but Dr. Watson is no longer part of server 2k8 and our infrastructure team has had issues getting it running on 2008. Are there alternatives that can be used in a similar way? In particular, we'd need the faulting module and address causing the crash (we use this with the PDB and map information to backtrace to the faulting location), and it would have to work with windows services (including those running as localsystem). Thanks for any suggestions. You can configure Windows Error Reporting to

I have an application that is hosting some unstable third-party code which I can't control in an external process to protect my main application from nasty errors it exhibits. My parent process is monitoring the other process and doing "the right thing (tm)" when it fails. The problem that I have is that Dr. Watson is still detecting crashes in the isolated process and attaching to the processes on the way down to take a crash dump. This has the two problems of: 1. Dramatically slowing down the time that it takes for me to detect a failure because the process stays alive while the crash dump

In Windows environments ( XP and Win 7 ): What is the best way to automatically have a crash dump generated when processes crash on the system? Can an installer (MSI) package do this? One of the best way to have an automatic dump for any/specific process on Windows is to configure a set of entries in the registry. I tried the below on Windows 7 64 bit. Open notepad.exe, paste the below entry and save it as "EnableDump.reg". You can give any name you wish. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps] "DumpFolder"=hex(2)