Just starting to learn how to Debug

[Anak]

Hi everyone!

Under the advice of CarlTR6 I went to Captain Debugger, and downloaded the winsdk_web file.

When I went to start the install I hit the following warning. (See attachment)
when I go to: http://go.microsoft.com/fwlink/?LinkID=187668 it turns into this:Download .NET Framework

My question is, I already have .NET4 on my machine. Will this do a repair and install the missing components or will it un-install, and then do a complete re-install, one that will satisfy winsdk?

Is there anything else I need to look out for?

Steve

 

[Mashed1316]

Hello there, Anak!

Question: do you have .NET Framework 4.0 Client Profile or .NET Framework 4.0? because there's 2 different downloads in Microsoft's site

Download details: Microsoft .NET Framework 4 (Standalone Installer)
Download details: Microsoft .NET Framework 4 Client Profile (Standalone Installer)

Check that out and it'll probably solve your problem

 

[Anak]

Good question!

According to Control Panel\All Control Panel Items\Programs and Features, I have Microsoft .NET Framework 4.0 Client Profile.

So that would lead me to believe that I would need to go to your second link, and let it do its thing, right?
Then go back, and try the winsdk_web install.

I also looked in C:\ , and have:
C:\Windows\Microsoft.NET
C:\Program Files (x86)\Microsoft.NET\RedistList
C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.1

I added the SQL Folder because I'm not sure if it also has something to do with the Debugging Tool.

 

[Mashed1316]

Exactly! Install the .NET Framework 4 from the second link i posted, after installation, try to install the "winsdk_web install" and see if the problem is solved

I'm 99% sure that it'll work since you only have the .NET Framework 4 Client Profile installed, not the .NET Framework 4, thus, the error about not having the needed files for the SDK to install.

Please, report back

 

[Anak]

Well.... I downloaded the file from the second link and it offered me two options, repair or un-install. I picked the first for a repair let it do its thing, did a reboot then tried the winsdk_web install again.

The same setup note popped up, and I thought, what? So I re-read the message again carefully, and the yolk's on me .

winsdk needs the full version of .NET frame4, not the Client so I need to download from your first link, and then try winsdk again.

Not sure when I'll get back, been busy with snow removal, helpin' the DW, and neighbors.
25°F -2°C dropping to 8°F -12°C tonight.

How's the weather in Venezuela?

Life is what happens to you when your busy making other plans....
(John Lennon, "Beautiful Boy" English singer & songwriter (1940 - 1980)

 

[Mashed1316]

Daaaaaaaaaaaaaamn hahaha... that's cold.. well Steve, in Venezuela we have a tropical weather.. i'm actually 30mins away from the caribbean shore.. right now it's 21ºC with 10mph winds and 69% of humidity hehe, it's "fresh" because i'm used to it.. been living here for 21 and a half years haha...

BTW, yeah.. i confused the links! sorry you had to download the 2nd one, actually is the first one that you need to download and install!

Ok, i'll be waiting for your report

 

[Anak]

Okay!

I have the full version of .NET4 installed and started with the winsdk install, but when it came to what all I wanted to install I was not sure what I really needed for just doing debugging.

(See attachments) I had to do two pix so you could see the whole list.

At the present time I have no plans for getting involved with:

• Windows Native Code Development or
• .NET Development

In the Common Utilities Block,
I can see installing the Debugging tools for Windows, and maybe the other three.

In the second pix, the Redistributable Packages block it is asking to install Microsoft Visual C++ 2010.

I already have (See third attachment) C++ installed, albeit, they are the 2005, and 2008 versions.
Are those versions sufficient for Debugging?

So, again I ask; What do I really need for just doing debugging?

 

[Mashed1316]

Well, to be completely honest, i know ZERO about Debugging, but i do recommend that you install all the features, i mean.. they got to do something :huh:

If i were you, i'd install the whole thing just to be sure.. and to narrow the error margin!

Let me know how it works out

 

[Anak]

To satisfy my curiosity, would you be offended if I asked for an opinion from some of the regular debugging gurus?

 

[Maguscreed]

I would personally add all the redist packages, I forget exactly what is under tools but I seem to remember expanding that and changing one or two items. It's been a bit since I did it though.

 

[Mashed1316]

No, of course not Steve.. that's why they're there hehe.. i'm just a regular guy trying to solve your issue i'm more of a Video Cards/RAM/HDD/OS Installation kind of guy.. don't worry

Actually i would like to see a Debugging Guru here for some explanations, that way i'd learn more about it

 

[Anak]

Thank you Punkster. I will make a post now. Expect something in a few hours.

 

[DeanP]

What I did, was that I just install those two Debugging Tools, I got my .NET framework installed separately.

You will need to fill in the symbol file path in Debugging before you can start debug dump files.

Let me know or a BSOD guru know if you need any more questions...

 

[Anak]

Thank you both Maguscreed , and DeanP, help has been asked for.

DeanP, what were the names of those two tools?

 

[DeanP]

Debugging Tools for Windows and Debugging Tools

 

[Anak]

Okay, I see the one in the Common Utilities Block, the Debugging tools for Windows.

In the second pix, the Redistributable Packages block I see the Debugging Tools.

I'm going to wait though, for a reply to my question.

Thanks DeanP......Steve

 

[DeanP]

Here's some things about debugging dump files

- Program is called WinDbg
- Requires a symbol file path in order to view dump files.
- Use command "lmtsmn" to view list of drivers from A to Z including date.
- Magic date for Windows 7 Drivers is July 13, 2009 (any before the date requires update)
- secdrv.sys and amdxata.sys are the two drivers that are not required to update.
- Sometimes - A dump file may not be created during a BSOD. You will need to find another source...
- when you see windows core file blamed for bsod (win32k.sys, csrss.exe, ntrknrlmp.exe, etc...), usually caused by third party anti-virus.
- third party anti virus, old drivers, faulty hardware can use BSOD.

Hope this helps...

 

[reventon]

All that is necessary is the "Debugging Tools for Windows" shown in your screenshot below (under "common utilities").

I did install a few other items too - but they are unrelated to Windbg and not needed to debug BSODs.

 

[fimble]

The Redistributable Package are software installers, like you are looking at.

You could in fact, download only the Redistributable Package Debugging Tools, close and throw away the installer you are now using and then run the Debugging Tools Redistributable Package to install WinDBbug. (Apart, of course from anything else you need for WinDbug to work!!)

 

[CarlTR6]

Anak, see if this link helps you to understand: Windows Debugging Tools and Symbols for Driver Developers: Getting Started