Skypher » Debugging http://skypher.com The blog for absolutely nothing! Sat, 19 Nov 2011 22:09:02 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 JIT Debugging 32-bit applications on 64-bit Windows http://skypher.com/index.php/2009/08/27/jit-debugging-32-bit-applications-on-64-bit-windows/ http://skypher.com/index.php/2009/08/27/jit-debugging-32-bit-applications-on-64-bit-windows/#comments Thu, 27 Aug 2009 08:08:19 +0000 SkyLined http://skypher.com/?p=176 Warning: preg_split() [function.preg-split]: Compilation failed: lookbehind assertion is not fixed length at offset 14 in /home/c3682jgn/domains/skypher.com/public_html/wp-content/themes/braille/options/plugins.php on line 77

Warning: Invalid argument supplied for foreach() in /home/c3682jgn/domains/skypher.com/public_html/wp-content/themes/braille/options/plugins.php on line 78
]]> I found that using the x64 Debugging Tools to debug x86 applications on 64-bit windows can lead to all kinds of problems. I recently installed both the x64 as well as the x86 Debugging Tools side-by-side on my system, so I can use the x86 debuggers for 32-bit applications and this seems to solve all my problems. Setting up just-in-time debugging to use the x86 debugger for 32-bit applications and the x64 debugger for 64-bit applications can be done through using regedit.exe. On x64 versions of windows, the “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug” key is used for JIT debugging 64-bit applications and the “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug” key is used for 32-bit applications. This means you can set one to the x64 debugger and the other to the x86 debugger. Here’s is an example .reg file that does exactly this:


Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug]
“Debugger”=”\”C:\\Program Files\\Debugging Tools for Windows (x64)\\windbg.exe\” -p %ld -e %ld -g”
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug]
“Debugger”=”\”C:\\Program Files (x86)\\Debugging Tools for Windows (x86)\\windbg.exe\” -p %ld -e %ld -g”

This sample file can be downloaded here.

In a previous post, I described how to create explorer integration for WinDbg. If you have both the x86 and the x64 Debugging Tools installed, you may want to be able to choose which debugger you open an application with. This can be achieve by creating two entries, one for the x86 debugger and one for the x64 debugger. Here is an example .reg file that does this:


Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg x86]
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg x86\command]
“IsolatedCommand”=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
46,00,69,00,6c,00,65,00,73,00,28,00,78,00,38,00,36,00,29,00,25,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,77,00,69,00,6e,00,64,00,\
62,00,67,00,2e,00,65,00,78,00,65,00,22,00,20,00,2d,00,6f,00,20,00,2d,00,73,\
00,66,00,6c,00,61,00,67,00,73,00,20,00,30,00,78,00,38,00,30,00,30,00,33,00,\
30,00,32,00,33,00,33,00,20,00,2d,00,57,00,20,00,53,00,6b,00,79,00,4c,00,69,\
00,6e,00,65,00,64,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
@=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,\
00,65,00,73,00,28,00,78,00,38,00,36,00,29,00,25,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,77,00,69,00,6e,00,64,00,62,00,67,00,2e,\
00,65,00,78,00,65,00,22,00,20,00,2d,00,6f,00,20,00,2d,00,73,00,66,00,6c,00,\
61,00,67,00,73,00,20,00,30,00,78,00,38,00,30,00,30,00,33,00,30,00,32,00,33,\
00,33,00,20,00,2d,00,57,00,20,00,53,00,6b,00,79,00,4c,00,69,00,6e,00,65,00,\
64,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg x64]
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg x64\command]
“IsolatedCommand”=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,\
46,00,69,00,6c,00,65,00,73,00,25,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,36,\
00,34,00,29,00,5c,00,77,00,69,00,6e,00,64,00,62,00,67,00,2e,00,65,00,78,00,\
65,00,22,00,20,00,2d,00,6f,00,20,00,2d,00,73,00,66,00,6c,00,61,00,67,00,73,\
00,20,00,30,00,78,00,38,00,30,00,30,00,33,00,30,00,32,00,33,00,33,00,20,00,\
2d,00,57,00,20,00,53,00,6b,00,79,00,4c,00,69,00,6e,00,65,00,64,00,20,00,22,\
00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
@=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,\
00,65,00,73,00,25,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,36,00,34,00,29,00,\
5c,00,77,00,69,00,6e,00,64,00,62,00,67,00,2e,00,65,00,78,00,65,00,22,00,20,\
00,2d,00,6f,00,20,00,2d,00,73,00,66,00,6c,00,61,00,67,00,73,00,20,00,30,00,\
78,00,38,00,30,00,30,00,33,00,30,00,32,00,33,00,33,00,20,00,2d,00,57,00,20,\
00,53,00,6b,00,79,00,4c,00,69,00,6e,00,65,00,64,00,20,00,22,00,25,00,31,00,\
22,00,20,00,25,00,2a,00,00,00

(Note: these entries also add specific command-line options that I like to use – you can use regedit.exe to remove or change them to whatever you want).

This sample file can be downloaded here. If you installed my previous implementation of explorer integration, you may want to delete the “HKEY_CLASSES_ROOT\exefile\shell\WinDbg” key to remove it. Otherwise you’ll have three WinDbg options to choose from, two of which are duplicates and do exactly the same thing.

]]> http://skypher.com/index.php/2009/08/27/jit-debugging-32-bit-applications-on-64-bit-windows/feed/ 0 WinDbg explorer integration http://skypher.com/index.php/2009/01/05/windbg-explorer-integration/ http://skypher.com/index.php/2009/01/05/windbg-explorer-integration/#comments Mon, 05 Jan 2009 09:16:57 +0000 SkyLined http://skypher.com/?p=82 Warning: preg_split() [function.preg-split]: Compilation failed: lookbehind assertion is not fixed length at offset 14 in /home/c3682jgn/domains/skypher.com/public_html/wp-content/themes/braille/options/plugins.php on line 77

Warning: Invalid argument supplied for foreach() in /home/c3682jgn/domains/skypher.com/public_html/wp-content/themes/braille/options/plugins.php on line 78
]]> You can execute any .exe file (and link to .exe file, with arguments) running under WinDbg by right clicking it and selecting “WinDbg” by adding the following to your registry:

Create the key “HKEY_CLASSES_ROOT\exefile\shell\WinDbg\command” and set the default value to a REG_EXPAND_SZ with this value:

“%ProgramFiles%\Debugging Tools for Windows (x64)\windbg.exe” -o -W [Your workspace] “%1″ %*
 

-or-

“%ProgramFiles%\Debugging Tools for Windows (x86)\windbg.exe” -o -W[Your workspace] ”%1″ %*
 

(Choose the  x64 or x86 version depending on your OS).
The option “-W [Your workspace]” tells Windbg to use a specific workspace and “-o” option tells WinDbg to also debug child processes started by the .exe. You can omit both options if you prefer.

Here’s an example .reg file for x64 that uses the “SkyLined” workspace, you can use it to get started and modify the key using regedit to fit your needs. It can be downloaded here:

Windows Registry Editor Version 5.00
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg]
 
[HKEY_CLASSES_ROOT\exefile\shell\WinDbg\command]
@=hex(2):22,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,\
6c,00,65,00,73,00,25,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,36,00,34,00,29,\
00,5c,00,77,00,69,00,6e,00,64,00,62,00,67,00,2e,00,65,00,78,00,65,00,22,00,\
20,00,2d,00,6f,00,20,00,2d,00,57,00,20,00,53,00,6b,00,79,00,4c,00,69,00,6e,\
00,65,00,64,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00
 

]]> http://skypher.com/index.php/2009/01/05/windbg-explorer-integration/feed/ 2