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

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

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. !heap failed in windbg. Invalid type information f
(Forum/Crash Dump Analysis )

... (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. [ ... skipped ... ] 0:042> vertarget Windows Server 2003 Version 3790 (Service Pack 2) MP ...

4. Brand New to Windbg - Need some basic answers
(Forum/Kernel-Mode Debugging)

... this doable by using the Windbg debugger? I simply want to set breakpoints at the calls into the bios to trace the register settings, etc. Any help that could be offered would be appreciated. th ...

5. 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 ...

6. Crashdump bitness
(Forum/General Questions)

Hi, Is there a way to find out if a dump was created using 32bit or 64bit debugger? Thanks Nachiket ...

7. Creating custom disassembly-like window in an ext
(Forum/Writting Extensions)

... sdk. The only mention I could find is about generating custom output (custom foreground/background I assume). The manual also mentions that windbg itself is built on top of the debugger engine (dbgeng.dll ...

8. Help with crash dump
(Forum/Crash Dump Analysis )

... kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000140, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 804eb5b9, ...

9. 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 ...

10. Re: drwtsn32
(Forum/General Questions)

... crashes over to MS just to retrieve them later anyway. To achieve this add the following string value for AeDebug\Debugger in the registry: "C:\WINDOWS\system32\ntsd.exe" -p %ld -e %ld -g -c ".dump ...

11. Re: kernel32 symbol in live kernel debug
(Forum/Symbol and Source Files )

... process should load kernel32.dll; applications that have a GUI also load user32.dll). Symbols are loaded into a debugger mainly for two purposes: What you are asking about somehow violates this basic ...

12. 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 ...

13. Re: Random Thread getting stuck
(Forum/User-Mode Debugging)

Hi Ben, Have you solved this problem? According to the call stack, the thread is waiting for something. If you can attach a debugger, try kb and !handle to see the objects which block the thread. ...

14. Re: Remote debugging of CrashMe with ntsd -d
(Forum/Article Discussions)

Guillaume, welcome. My experience is that it is often not worth to debug user mode applications from a kernel mode debugger. True, the official docus propose to debug Winlogon just as you did. But hey, ...

15. 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 ...

16. Re: Symbol not found
(Forum/Symbol and Source Files )

... not /ZI (Program Database for Edit & Continue) - use the !sym noisy WinDbg command (debugger displays info about its search for symbols), followed by ld * - check out other symbol-related commands ...

17. 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 ...

18. 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 ...

19. 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, ...

20. 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 ...

21. 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 ...

22. 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 ...

23. 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 ...

24. Symbol not found
(Forum/Symbol and Source Files )

hi every one, i have recently moved from Ms VS debugger to Windbg (which i got from win SDK ver 7) ,and i'm facing the well known beginners problem which is setting the path for the debug symbol file: here ...

25. WinDbg showing Wrong Info
(Forum/User-Mode Debugging)

... an old PDB against a nwer version of the EXE). Also, I'm using the old RaiseException trick to name my threads in the debugger, yet sometimes I only see some of my threads with names in WinDbg even ...