Configuring the "Debugging Tools"

[HoneycombAG]

Symbol file path could not be found

I keep getting told that the Symbol File Path could not be found as of recent. What happened?

 

[Arc]

Hello mate, I also have got it once. Frederick guided me to reinstall WinDBG again, and set the symbol path as fresh.

It worked like a charm, amd nowadays there is no issue with the symbol path at all.

I wish it will work for you too. Best of luck

One more thought, the standalone tool does it much more often.

 

[HoneycombAG]

You know, taking another long look at this tutorial, I find out I haven't been saving my workspace. Not that it matters but it nags every time I open something for bug checking. Also, where do I look to obtain third-party file symbols?

 

[Vir Gnarus]

I've had to deal with the nagging workspace problem as well. Sometimes I've found if I manually go to Options and tell it to Never save for Workspace Prompts, then save Workspace As... and name it Default, that works. Probably best to do this when no dmp file is loaded and it's just a blank Windbg session. This is what has worked for me in the past, though results may vary.

 

[LukeG224]

Would it be possible to upload my dump files to see why I keep getting BSoD?

 

[Arc]

Yes, possible, but make a new thread for it please.

 

[rovopio]

every couple months, my laptop returned a IRQL Less or Equal BSOD, i clean installed windows every few months.
Koolkat (tx for your tremendous help), analyze that the error was from the installation of my atheros wireless driver. i installed the driver from the CD driver that came from the notebook. and i updated the driver through that CD software as well.

i wanna learn debugging myself because i wanted to see whether my clean install still have that unclean driver installation or not. So, i wanted to know which file from the dump folder from the BSOD instruction did koolkat found my problem.

i assume its the dmp file and thats how i ended up on this thread.


Now i've read this thread and went to this link Download and Install Debugging Tools for Windows
which one should i download since there are many links available there.

the first download link available over there was this one Install Debugging Tools for Windows as part of the WDK
but since its written for windows 8 i decided to downloaded this one instead of that one
Download the Microsoft Windows SDK for Windows 7

under the second link there is another download link Download Windows Symbol Packages should i download this as well?

===
so far i have downloaded Download the Microsoft Windows SDK for Windows 7 and i got stuck on this step of this tutorial ==>
C:\debuggers>windbg.exe -IA

windbg.exe is not recognized as an internal or external command, operable program or batch file


did i download the wrong link? should i download the first link? and should i download the symbol package as well?

 

[Arc]

• 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?

 

[Vir Gnarus]

While the WDK for Windows 8 caters to that OS, the Debugging Tools that comes with it is the latest version of Windbg and can be installed on WinXP and above and will open any Windows crash dump from any Windows OS.

To explain Arc's method, he's telling you that your issue is that you need to first find the directory the debugger (Windbg) is installed, then open that directory in the command line and type the appropriate command to associate dump files with Windbg. You can simply navigate to the folder normally, then when you have it open, hold Shift and right click any white space in that folder and you'll have the option to "Open command window here". Then follow up with the Windbg.exe -IA.

 

[rovopio]

edited after reading vir gnarus reply

hi mates~! tq very very much for helping me

i downloaded Download the Microsoft Windows SDK for Windows 7 instead of Install Debugging Tools for Windows as part of the WDK

okay so... from vir gnarus explanation i take it i downloadded the wrong file? since what i get from my start windows is start => all program => debuggging tools for windows x64 and microsoft windows sdk v7.1

Secondly... i wrote on my previous post that i followed the tutorial so... i did not install it at the default path, (i was following the step on post#1 which ordered me to Override the default install path and install to c:\debuggers instead

so my path is c:\debuggers.

should i return the debugging tools path to where arc tells me it should i pointed to...? how do i do that?

or is it easier to just uninstalled the 7.1 kit and download the correct 8.0 kit? how do i uninstall the 7.1 kit by the way, i cant find it on revo uninstaller or control panel.

===
sorry for the big font, did not meant to use it at all

cheers,

KP~!

so... the correct link to download is it the 1st WDK link? or SDK link or the standalone component from this link http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx?

 

[Arc]

After opening an elevated command prompt, have you changed the directory as by typing
CD C:\debuggers ?

When you are at the proper directory, then only you can execute the next command as per the tutorial.

 

[rovopio]

yea i did that and i got windows cannot find the file path specified.

so i wrote C:\>chdir /d C:\debuggers instead.

I am here now, C:\debuggers>windbg.exe -IA
and i got that internal external command etc etc

do i need to download the proper 8.0 debugging tools btw? or the stand-alone 7.1 i've downloaded and put on the wrong path worked just as well?
I'm downloading the debugging tools part of WDK as we speak, i hope its the correct one

===
btw, i posted on my BSOD thread regarding uninstallation of driver and getting rid of asus utility, kindly check it out at your leisure

cheers,

KP

wish you a great week!!

 

[Arc]

Try it: Debuggers (x64)

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

 

[rovopio]

Even if the dumps are not associated with windbg, you can open windbg, then File > Open Crash Dump and browse to the dump and open it. The result will be the same.

i tried this as well since its on post#1,, there are 2 dump file on my dump folder, when i opened 1 of them,, i got a pop up saying "executable search is:" and it doesnt open just stay that way.

when i opened the other one, i got "you dont have to correct symbols" or smthn... i cant rmmbr what.


on that note, i will try downloading your link and go from there,


cheers again,


KP~!

 

[Arc]

Open windbg.
Go to File > Symbol Path File.
In the box, paste it : SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
If it is prompted to save the workspace, uncheck the box and save.

All done.

 

[rovopio]

okay i've tried opening the crash dump file, and its already associated with dmp files, the windbg.exe -IA command works properly this time, however when i tried opening dump files, i got

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:

and that's it. also on the bottom it was written, debuggee not connected.

may i ask wht should i do now?

 

[Arc]

and that's it. also on the bottom it was written, debuggee not connected.


may i ask wht should i do now?

Wait a bit .... till a line comes saying "Followup : machineowner" or something similar. It's a break point, and then you will get KD against the place to type further commands.

 

[Vir Gnarus]

If you set things up correctly (which from the looks of it you did), what's happening is it's downloading all the symbol files and storing it in the folder you assigned (C:\SymCache). It will take a while, especially for the first run, so let it sit. May even take several minutes, depending on your network connection. Once it's done, the "debuggee not connected" will disappear and it'll provide the prompt and will not give any big symbol errors.

Some symbol errors are expected for drivers that are 3rd-party drivers, since they very commonly do not include symbols (nor will MS have it in their symbol server). What you'll want to worry about is when it pops up that it couldn't find symbols for Windows modules. When that happens usually it'll prompt you with a big massive message about no or incorrect symbols.

 

[rovopio]

awesome, i think it takes a quite long while due to slow internet connection then.

i will post my result on the appropriate thread,

cheers for the help!!

KP

 

[Arc]

Then the SymCache will be developed, it will not take very long to complete a breakpoint.