Add Windbg (kd>) Commands to Program Default for Dump Files

[jcgriff2]

Most of us have Windbg set up as the default program for dump files - Register Windbg for dump files (File Associations)

Did you know that you can also add kd commands to run by default as well?

Simply setting up Windbg as the default program leaves Windbg at this point after double-clicking on a dump file -- waiting for you to enter additional commands at the kd> line such as !analyze -v -

[FONT=Lucida Console]*******************************************************************************[/FONT]
[FONT=Lucida Console]*                                                                             *[/FONT]
[FONT=Lucida Console]*                        Bugcheck Analysis                                    *[/FONT]
[FONT=Lucida Console]*                                                                             *[/FONT]
[FONT=Lucida Console]*******************************************************************************[/FONT]
[FONT=Lucida Console] [/FONT]
[FONT=Lucida Console]Use !analyze -v to get detailed debugging information.[/FONT]
[FONT=Lucida Console] [/FONT]
[FONT=Lucida Console]BugCheck 50, {fffff80011b0e74d, 8, fffff80011b0e74d, 2}[/FONT]
[FONT=Lucida Console] [/FONT]
[FONT=Lucida Console]Could not read faulting driver name[/FONT]
[FONT=Lucida Console]Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43346 )[/FONT]
[FONT=Lucida Console] [/FONT]
[FONT=Lucida Console]Followup: MachineOwner[/FONT]
[FONT=Lucida Console]---------[/FONT]

I changed my default set up to include these commands -

[FONT=Lucida Console]!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck[/FONT]

So, when I double-click on a dump file, all of the basic commands that I like to run do so without me having to enter them at the kd> command line.

Try it out!

Back up your registry first (I opted to create a system restore point).

Maneuver to this registry key and add your default Windbg commands -

[FONT=Lucida Console]HKLM\SOFTWARE\Classes\WinDbg.DumpFile.1\shell\Open\command[/FONT]

The (Default) should look something like this (by default):

[FONT=Lucida Console]"C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\windbg.exe" -z "%1"[/FONT]

I added the kd commands that I mentioned above:

[FONT=Lucida Console]"C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\windbg.exe" -z "%1"[COLOR=#ff0000] -c "!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck"[/COLOR][/FONT]

Double-clicking on a dump file now runs all of the commands in RED by default.

Please note that I made these changes yesterday for the first time, so it is far from 100% tested.

Regards. . .

John

 

[philc43]

If anyone has started to use the new WinDbg Preview which is now available from the Windows Store in W10 you might be interested to know you can still add these same commands to run automatically after double-clicking on the dump file.

Back up your registry first or create a system restore point.

Manoeuvre to this registry key and add your default Windbg commands to the parameters string value, adding them after the -z "%1" as previously done

Computer\HKEY_CLASSES_ROOT\AppXh09fg0r1jvyz62yqhm5yw1v5jknrdxfr\Shell\open

A quick way to find the key is to use Find and search for WinDbg Preview, it will be the first one found from the top of the registry entries.

There is a clue in the name, this new version is a Preview and is being actively worked on and improved. Use the Feedback function to request any new features. I have to say that I like the more modern interface, basically it hasn't changed what I do but there appear to be some new features and my guess is this version will be updated at a faster pace than the old WinDbg.