WiLODbg: Working with latest WinDbg versions

Ozzy Godin — Mon, 22 Sep 2008 17:42:07 GMT

Wilodbg allows windows debugger to work over ILO and therefore save a debugging machine works against each DUT,

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=MTX-19733a0f542246f19e8f0b4004&jumpid=reg_R1002_USEN

Wilodbg utility won’t support the latest version of windbg unless HP will release an update or add the following reg key,
___

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\DebuggingTools]

"Release notes"=""

"Global Flags"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\

00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,44,00,65,00,62,00,75,00,67,00,\

67,00,69,00,6e,00,67,00,20,00,54,00,6f,00,6f,00,6c,00,73,00,20,00,66,00,6f,\

00,72,00,20,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,28,00,78,00,\

38,00,36,00,29,00,5c,00,00,00

"Debugging Help"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\

6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,44,00,65,00,62,00,75,00,67,\

00,67,00,69,00,6e,00,67,00,20,00,54,00,6f,00,6f,00,6c,00,73,00,20,00,66,00,\

6f,00,72,00,20,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,28,00,78,\

00,38,00,36,00,29,00,5c,00,00,00

"WinDbg"=hex(2):43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,20,\

00,46,00,69,00,6c,00,65,00,73,00,5c,00,44,00,65,00,62,00,75,00,67,00,67,00,\

69,00,6e,00,67,00,20,00,54,00,6f,00,6f,00,6c,00,73,00,20,00,66,00,6f,00,72,\

00,20,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,28,00,78,00,38,00,\

36,00,29,00,5c,00,00,00

[HKEY_CURRENT_USER\Software\Microsoft\DebuggingTools\AddRemove]

"ProductCode"="{D59967FF-4DCC-4695-BCD9-FA47B94047D6}"

___

on old version of WinDbg (Before 6.9.3.113) there was a registry key "HKEY_CURRENT_USER\Software\Microsoft\DebuggingTools" which hold the install path of the WinDbg.
I latter version, this key doesn't exists anymore and was replaced by other keys.
The problem is that the WiloDbg fails to start in case it doesn't find the "missing" reg key.
The complete solution is that WiloDbg will "know" that this key is gone and will look for the information in other keys exists that tells where WinDbg is installed.

topic WiLODbg: Working with latest WinDbg versions in Server Management - Remote Server Management

WiLODbg: Working with latest WinDbg versions