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

...  21) Application Verifier 6) Main extensions 14) Tracing and stepping (F10, F11) 22) Logging extension (logexts.dll) 7) Symbols 15) Call stack 8) Sources ...

2. CrashMe Application
(Applications and Tools/General Applications)

... binaries, symbols, and sources Note: If you have an interesting situation that CrashMe doesn't cover please drop us a line or send us your code. Other CrashMe fans might be thankful for your contribution. ...

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

... "WinDbg. From A to Z!" turns out to be just as useful as WinDbg itself because it explains everything from simple things that you should know right away such as setting up symbols and the theory of command ...

4. ASP hang
(Forum/Crash Dump Analysis )

... pool. The server is Windows 2003 and IIS6. Many thanks in advance. Here's the output: 0:000:x86> !analyze -v *** WARNING: symbols timestamp is wrong 0x499007dc 0x49900d5a for ntdll.dll ******************************************************************************* * ...

5. Bugcheck Analysis
(Forum/Crash Dump Analysis )

... Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel ...

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

Kam, In general you don't need symbols to know the entry point of a PE image. The entry point is conveniently stored to the PE header and can be read from it. Further the OS loader loads an image into ...

7. Re: Unable to load image ntkrnlpa.exe
(Forum/Crash Dump Analysis )

... symbols from Microsoft's symbols server. We have download the symbols to an identical Stratus server and ran the livekd kernel dump successfully...even moving the symbols directory/path around at will. ...

8. Re: Unable to load image ntkrnlpa.exe
(Forum/Crash Dump Analysis )

... a hex-editor for example? We need to run a kernel dump (we are using livekd) on a secure Status server that we CANNOT open up to the internet in order to download symbols from Microsoft's symbols ...

9. Re: Unable to load image ntkrnlpa.exe
(Forum/Crash Dump Analysis )

... the symbols on the 'open' server and test them on a test 'secure' server successfully. We now need to find out if there will be a descrepancy between Windows Server 2003 R2 sp2 and Windows Server 2003 ...

10. Re: Unable to load image ntkrnlpa.exe
(Forum/Crash Dump Analysis )

Chris, you are welcome. I hope you applied correct symbols to all your environments in the meantime. I didn't try it but I guess you ended up with two different symbol sets for Windows Server 2003 ...

11. Re: Unable to load image ntkrnlpa.exe
(Forum/Crash Dump Analysis )

There does NOT appear to be a descrepancy for the 'R2' variant. We were able to sucessfully download symbols from Microsoft Symbols Server on server A and import/utilize them on server B. The symbols ...

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

JD, welcome. Whenever you see a large offset like this mydll!wrongfuncanme+0x33360 it is always a sign of missing symbols. Now strncpy is part of the CRT library and thus resides in MSVCR80.DLL ...

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

... kernel32, and other system DLLs, you wont see function parameters or local variables for these functions. Note that MS releases only public symbols for their modules. For local variables or function ...

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

... internal symbols tables. In fact the SDbgExt extension does something similar; it reads MAP files generated by a MS linker and feeds that information to WinDbg. Obviously a MAP file doesn't contain as ...

15. Re:Unable to load image ntoskrnl.exe
(Forum/Crash Dump Analysis )

... path: "srv*;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols" -> "srv*c:\Symbols*http://msdl.microsoft.com/download/symbols" I don't know if the first srv*; can confuse WinDbg; in any case it ...

16. Unable to load image ntoskrnl.exe
(Forum/Crash Dump Analysis )

... Dump File: Only registers and stack trace are available Symbol search path is: srv*;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image \WINDOWS\system32\ntoskrnl.exe, ...

17. windbg question
(Forum/Article Discussions)

Hi, Let's say that the driver I want to debug doesn't have symbols, so I can't use DriverEntry. !lmi 77fba431 (same problem: address not found (so name is interpreted as hex)) Also, the problem ...