Configuring the "Debugging Tools"

stevieray said:

Thanks Geo64 and zigzag! Got it to work!

For any noobs who follow:
1. Open a command prompt as an admin, that'll give you:
"C:\Windows\system32>"

2. Enter "chdir /d C:\debuggers"... this will give you a new prompt "C:\debuggers"

3. Enter "windbg.exe -IA" and Et Voila!

Thanks again guys!

It isn't working for me ..

I get this:

Code:

C:\Windows\system32>chdir /d C:\debuggers

C:\debuggers>windbg.exe -IA
'windbg.exe' is not recognized as an internal or external command,
operable program or batch file.

C:\debuggers>windbg.exe -IA
'windbg.exe' is not recognized as an internal or external command,
operable program or batch file.

C:\debuggers>

Edit:

Okay I jumped back to post #48 to find out a little more about why it isn't working for me.

Arc said:

• Expand the start menu to :
  Start > All Programs > Windows Kits > Debugging tools for Windows (x64)
• Right click on Windbg (x64) > Properties .
• Look at "targrt". If you installed at the default path, the tagret is :
  "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe"

Open the command prompt.

• Type -- CD C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64 and hit enter.
• When the directory is accordingly changed, type windbg.exe -IA

Is it done now?

but I don't have a Windows Kits in my start programs

Shouldn't I have it since I grabbed it from here: Windows Driver Kit (WDK) and Debugging Tools for Windows (WinDbg) downloads

I just checked the folder C:\debuggers I made and there are no files in it. I don't know why.. I did install it. What am I doing wrong? (default is C:\Program Files\Microsoft SDKs\Windows\v7.1 but I changed it on the advice earlier in this thread to make it easier to find and all).

I even TRIED to let it go to the default C:\Program Files\Microsoft SDKs\Windows\v7.1 and it is not there neither ..

I even tried what was suggested here:

Arc said:

Try it: Debuggers (x64)

A bit older version, but works exactly the same. Contains the debugger tool only and nothing more.

But I get this:
"Please insert the last disk of the Multi-Volume set and click OK to continue. "

I also tried the stand alone ..

Get this one and follow the instructions of the initial posts.

Some places to get windbg got their nature changed over the passage of time.

Arc said:

Get this one and follow the instructions of the initial posts.

Some places to get windbg got their nature changed over the passage of time.

Ah okay good thank you! Now I can use the debugger to figure out why IELowutil.exe keeps on stopping.

You are welcome. :)

Open a blank instance of WinDBG, then press Ctrl+S.

Does the Windows that opens, look like this?

FWIW, I needed to change something in Powershell to get this command to work.

Another entirely optional step that makes life easier. By registering WinDBG (the main debugger you'll want to use) as the default handler for common dump file types, you'll be able to double-click on a dump and have it open in WinDBG without having to go through the "File | Open..." menu operation every time. This registration needs to be performed from an elevated CMD prompt (run CMD as administrator):
C:\>cd debuggers
C:\debuggers>windbg.exe -IA

I needed to navigate to c:\debuggers\debuggers\x64\ then type the command as .\windbg.exe -IA
and that worked for me.