Is it possible to include WinDbg in the list of debuggers shown by vsjitdebugger when the latter is configured as the default debuuger in HKLM...\AeDebug?
Ideally I would like to be able to include a few more command-lines to the list of choices in vsjitdebugger that are available when a process encounters an unhandled exception: using DrWatson or using WinDbg to save a minidump for later inspection.
When WinDbg is in dormant mode, you can attach to a running process by choosing Attach to a Process from the File menu or by pressing F6. In the Attach to Process dialog box, select the process you want to debug, and select OK.
Launch Notepad and attach WinDbg In the Open Executable dialog box, navigate to the folder that contains notepad.exe (typically, C:\Windows\System32). For File name, enter notepad.exe. Select Open. The symbol search path tells WinDbg where to look for symbol (PDB) files.
To set the postmortem debugger to WinDbg, run windbg -I . (The I must be capitalized.) This command will display a success or failure message after it is used. To work with both 32 and 64 bit applications, run the command for the both the 64 and 32 debuggers.
There used to be such an (undocumented) option, up until VS7. The interface was a tool called vs7jit.
It was also discussed here, and the other directions brought up there may still be valid - specifically, the John Robbins 'Debugger chooser' code.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With