|
|
|
|
|
|
| |
|
Review
Windows Debugging Tools are as its name says, a group of command line and graphic tools and debuggers for Windows NT, 2000, XP and Vista. Its help file is really big due to the amount of information and reports you could do with it, however the most common usage (windbg) is to troubleshoot stop errors (bluescreens of death) using error libraries called symbols and reading the information from memory dumps located on C:\Windows\minidump.
Microsoft provides symbols in two ways
- through a webservice (configured on the tool) that will download symbols automatically when needed from http://msdl.microsoft.com/download/symbols
- Individual Installation Packets, that should be downloading for specific windows and debugger versions, available here:
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx.
However Windows Debugger have more tools to troubleshoot diferrent issues, for example
· cdb: C Language debugger
· ntsd: A just in time debugger, those that open inmediately an application crashed,
· tlist: a command to list tasks or processes
· gflags: Debugs exe applications
· adplus: same as fglags
· UMDH: Debugger for memory leaks
· symcheck: Visual Studio debugger. |
- Can help you determine if you got an stop error due to a hardware failure, driver or software.
- Its free
|
- Not friendly for the common PC User
- Some Reports are inconclusive
- Require internet connection or to download a big symbol file.
|
|
Reviewed by: Jean De Los Santos Reviewer rating:  |
|
|
Screenshots
|
|
