Whenever my application throws an unhandled exception, I would like WinDbg to catch that exception on my debugging machine rather than Dr. Watson, etc. How can this be configured?
Run windbg -I
to install it at the default post mortem debugger.
As Kurt points out below WinDbg comes in both 32 and 64 bit versions. Executing windbg -I
sets up the post mortem debugger for the processes corresponding to the bitness of the debugger.
You can install both versions of WinDbg side-by-side if you need to have both the 32 and 64 bit versions available.
From the help file:
-I[S]
Installs WinDbg as the postmortem debugger. For details, see Enabling Postmortem Debugging. After this action is attempted, a success or failure message is displayed. If S is included, this procedure is done silently if it is successful; only failure messages are displayed. The -I parameter must not be used with any other parameters. This command will not actually start WinDbg, although a WinDbg window may appear for a moment.