1. Common WinDbg Commands (Thematically Grouped)
(Documents/Command Lists)

...  19) Manipulating memory ranges 4) Expressions and commands 12) Thread related information 20) Memory: Heap 5) Debugger markup language (DML) 13) Breakpoints ...

2. WinDbg. From A to Z!
(Documents/Presentations)

... and learning curve. After all, it is very easy and comfortable to work with the Visual Studio debugger once you begin to use it. Those who advocate the use of a unified tool that does everything, like ...

3. Bugcheck Analysis
(Forum/Crash Dump Analysis )

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\060510-19390-01 begin_of_the_skype_highlighting              060510-19390-01      end_of_the_skype_highlighting.dmp] Mini ...

4. Re: break on driver load - question from kam
(Forum/Article Discussions)

... any driver with the name 77fba431 and [u]before calling its entry point. Here is what happens: 0: kd> .lastevent Last event: Load module 77fba431.sys at ba644000 debugger time: Wed Mar 31 21:12:56.937 ...

5. Re: Memory Access errors in the Kernel
(Forum/Kernel-Mode Debugging)

... one. Typically, when you are doing kernel debugging, the only visible user-mode address space is the one that is associated with the current process. The .process command instructs the kernel debugger ...

6. Re: See in Memory Descriptor List whats on
(Forum/Kernel-Mode Debugging)

... more information from WinDbg. Attach WinDbg as a kernel debugger to the target machine and use the following commands: 0: kd> !verifier 1 Driver Verification List Entry State NonPagedPool ...

7. Re: Wrong display of function Names by WinDbg
(Forum/User-Mode Debugging)

... check out the .symfix+ command... If you aren't able to get the right PDB files any serious debugger will read at least the export symbols (functions) of your modules. Example: If you open MSVCR80.DLL ...

8. Re:Can all commands be watched with WinDbg
(Forum/General Questions)

... WinDbg.exe into the same directory). > Image File (tab) - > Image -> enter the patch of your executable, i.e.: "C:\CrashMe.exe" - > Debugger -> enter the path to WinDbg, for example: "C:\Program Files\Debugging ...

9. Re:Can handled exceptions be seen with WinDbg
(Forum/Debugging of Managed-Code )

... perspective of the exception dispatcher there are two different situations to cover: In case there is a debugger the exception dispatcher does the following: The bottom line: if a debugger is attached, ...

10. Re:Can macros be set up in WinDbg
(Forum/General Questions)

Hi Will, welcome. Short answer: Yes. Long answer: WinDbg offers a quite powerful mechanism called "Debugger Commands Programs". In fact this is a simple script-language where you can use all commands ...

11. Re:Debugging minGW/GCC built DLL in Visual Studio?
(Forum/Symbol and Source Files )

Edward, welcome. The short answer is it depends. PDB is Microsoft's proprietary format and is not documented. While MS offers APIs to read and extract data from PDBs (see DIA SDK - Debug Interface Access ...

12. Re:How do source code files help?
(Forum/Debugging of Managed-Code )

... in the latest debugger release . The only WinDbg release really supporting it was version 6.7.5.0 which was mistakenly made public. Maybe you can still find it somewhere. If so, you'll be able to see call ...

13. Re:Question about COFF deprecation
(Forum/Symbol and Source Files )

... in the PEs is mainly intended for use by the Windows loader, a debugger actually needs more information to provide human readable information to us. This is where symbol files come in handy. Symbol files ...