Making it easier to debug .net dumps in windbg using .cmdtree
John Robbins beat me to the punch and wrote an excellent post about using .cmdtree in windbg to ease some .net debugging pain in windbg.
The windbg .cmdtree command allows you to create a popup window in windbg with commands that execute when you click on the respective link... so you no longer have to remember all the sos commands to get around in your managed dump.
Read his post here and with the command tree text file he provides you will be up and running in no time... You can also add the command .cmdtree c:\util\sos-cmdtree.txt once you have this set up, to your commands file to get it loaded automatically when you open dumps.... And of course, you can easily customize your commandtree so that you can execute any commands you like.
Really sweet,
Tess
Comments
Anonymous
September 17, 2008
The comment has been removedAnonymous
September 18, 2008
agreed:)Anonymous
September 18, 2008
The comment has been removedAnonymous
September 18, 2008
Chris, You've got an old version of WinDBG. Grab the 6.9.3.113 version from Microsoft and you'll get the .cmdtree command. John Robbins.Anonymous
September 18, 2008
I have the same problem that Chris does, but I have the latest version of WinDBG. The command works if I type it at the command window, but I cannot get it to work from the commands file. I get the 'Syntax error in .cmdtree sos-cmdtree.txt' error when WinDBG opens. Thanks, TimAnonymous
September 19, 2008
Tess - .cmdtree worked for 6.8.4.0 without any problem it was the startup commands.txt that didn't work. So for some reason, when its in a $< script, .cmdtree isn't working for me.Anonymous
September 20, 2008
Commands that are directed at windbg UI like .cmdtree don´t work from script files. SorryAnonymous
September 25, 2008
@Tim try to specify the full path, then it worksAnonymous
September 30, 2008
There is an undocumented feature in WinDbg that may be useful for remembering WinDbg commands and essentially