WinDBG: The very basics

[ICIT2LOL]

My command prompt opens a bit differently as you can see as I think my machine which has been getting slow and doing some strange things lately needs probably a reinstall?

 

[ICIT2LOL]

Tried plain cmd and got this - so do I uninstall and reinstall?

 

[ICIT2LOL]

Am going back to reinstall the WinKits as I seem to be getting nowhere here.

 

[derekimo]

You are copying Arc's 8.0 from the tutorial and yours is 8.1 John, try changing that part in the cmd box above.

See if that get's you to the next step.

 

[ICIT2LOL]

You are copying Arc's 8.0 from the tutorial and yours is 8.1 John, try changing that part in the cmd box above.

See if that get's you to the next step.

Ok Derek I will try in just a minute as I have just reinstalled WinKits as I think I may have done it wrong in the first place. On the laptop I had no hint of a problem and it worked perfectly.

 

[ICIT2LOL]

Hi John.

Follow this path ....

Start> All Programs > Windows Kits > Debugging tool for windows (x64)
​

When you are there, right click on WinDbg (x64) .... that is here ....

View attachment 327827
​

Now click "Properties" from the context menu. When the properties dialog will be open, you will notice that the "Target" is highlighted. Copy that target and paste it in your reply.

Now I have reinstalled I am getting this where you said Archie
"C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\windbg.exe"

I tried openeing a DMP file but nothing except the ref to look for another program to open it wirh.

Now it has occured to me that the laptop is running 8.1 and this machine 7 would that be the problem??

 

[Arc]

That should not be the problem. I think you are not doing it rightly.

Please take a time and do it slowly and carefully, step by step?

 

[ICIT2LOL]

That should not be the problem. I think you are not doing it rightly.

Please take a time and do it slowly and carefully, step by step?

Ok Archie I will do it again but I did take great care to follow it this time but will try once more.
I think maybe because I think I need a reinstall on this machine things are not going really that well.
It has got to be something like that because I did it on the laptop and it worked straight away.

 

[ICIT2LOL]

Now I am a little confused because it goes on to say download the SDK which I have - but when I run it I get the install window - see my pic and it says install it to this computer. But then a little further on it says now the Kit has been saved the FRAMEWORK must be installed first??
So you see my dilemma do I go right through with the WGB or install the FRAMEWORK the go back to the SDK download and run it??
It seems to me and no offence meant to Nommy or yourself that it should be the other way round -download and install FRAMEWORK and then run the install of the SDK??

 

[Arc]

Yes, winDbg always needs the dotnet framework to run. If it is already installed, then it will not be reinstalled. But the information will appear for sure.

Installing WinDbg is not enough to open dumps with WinDbg directly. What you have to open a crash dump with WinDbg is to use File > Open Crash dump.

But if you want to double click on a crash dump to open it with WinDbg directly, you have to configure the .dmp file association with WinDbg. And you have to follow the commands to do it properly.

 

[ICIT2LOL]

Yep I know what you mean Archie but what I was getting at was that the tutorial if followed to the letter as I did the first and second time - the instructions actually only gives me the option of installing the WinDBG first it does not let me make those changes and keep it as a download alone if I go that tick box level from there on it is all install.

It then asks for the FRAMEWORK to be installed. So in effect it is asking me to do something first that I should do second?
What I mean is should I install the FRAMEWORK first then go back and do the WinDBG stuff otherwise as I said the DBG is going to be installed when the tutorial is clearly asking me to install the DBG after the FRAMEWORK is installed and that is where I think it is all going pear shaped at my end.

But maybe I am reading it wrong and I am sorry if this is causing too much confusion if so I will not carry on trying because I am sure you have better things to do than muck about getting my head around this.

Now the only other thing that I can see to do is get to that tick box level minimise that and leave it at that - then install the framework and then go back maximise the WinDBG and finish off the WinDBG install?

 

[Arc]

You may install WinDbg anytime, but you will be able to access it when you have the latest version of dotnet framework installed.

Ordri of installation is not very important, you may do it as you want.

 

[ICIT2LOL]

Ok Archie it was just throwing me a bit because the order of doing it seemed a little like it should be the other way round.
I am leaving it for a while as I am off to my partners place for a while and will do it when I get back. I shall still be online with the laptop though - which installed this with no problems whatsoever and I can open the dump files but I still have to learn how to put them in posts like you blokes do.

But firstly I am sure I have to do a complete reinstall of the OS as things have not been quite right for some time now and I have tried all sorts of scans and tests and stuff that we normally tell others to do. I reckon the system has got that little bit corrupted somehow and why the WinKits stuff is not playing the game.

 

[Arc]

Hi John.

When the reinstall is done, get dotnet from filehippo. Download .NET Framework Version 4.5.2 - FileHippo.com
And Ger WinDbg from this place: WinDbg ..... the Debuggers (x64) one.

Everything will be installed smoothly, without any problem.

Then we may try for the file association again. OK?

 

[ICIT2LOL]

No worries Archie it may be some time before I get to be at home for a while though. Meanwhile the laptop here has got it running.

 

[Dude]

I loaded the symbol path and get this error?

 

[Arc]

Save the symbol path again. Then save the workspace before closing the the windbg window.

Now try to load the crash dump again. Does it work?

 

[Dude]

Save the symbol path again. Then save the workspace before closing the the windbg window.

Now try to load the crash dump again. Does it work?

Yes, that worked, thanks Archie

 

[Arc]

You are welcome mate.

 

[essenbe]

Welcome Doug, happy to see you here.