We're looking for a person or people to help audit MDN to find places we could speed up. Is this you or someone you know? Check out the RFP: https://mzl.la/2IHcMiE

How to get a stacktrace with WinDbg

The links provided for the 32-bit WinDbg are now redirected to a web downloader for the Windows SDK. You have to check Debugging Tools under Redistributable Packages in the installer, and then run C:\Program Files\Microsoft SDKs\Windows\v7.1\Redist\Debugging Tools for Windows\dbg_x86.msi, to install the 32-bit WinDbg. The page could make this clearer.

Updates made on 23 December 2009 by me (geeknik):

Added new FAQ entries based on the information that SteveE posted below.
Added new FAQ entries to deal with debugging issues on Windows 7.
Updated commands to provide more information in debugging logs.


Some feedback for this article:

1) First time I ran Windbg I had a dialog talking about workspaces ("Save information for workspace?"). I'd like to see a line of text on what to do.

2) After putting in the lines

.sympath SRV*c:\symbols*http://symbols.mozilla.org/firefox
.symfix+ c:\symbols
.reload /f

The command console reports:

Reloading current modules
.*** WARNING: Unable to verify checksum for firefox.exe

Shaver and timeless tell me this is normal, but it'd be nice for this MDC article to mention that it's expected. (Apparently "we don't checksum our modules")

Document Tags and Contributors

 Contributors to this page: rjohnson19, geeknik, Stevee
 Last updated by: rjohnson19,