Sometimes you need to get a stacktrace (call stack) for a Firefox crash or hang but Talkback fails because it's a special crasher or a hang. This article describes how to get a stacktrace in those cases with WinDbg on Windows.
To get such a stacktrace you need to install the following software:
Debugging Tools for Windows
Microsoft distributes the Debugging Tools for Windows for free, those include WinDbg which you will need here. Download it from for 32-bit versions of Windows (if you own a 64-bit version of Windows, follow the link on that page to the 64-bit version). Then install it, the standard settings in the installation process are fine.
A Firefox version for developers
You need a special Firefox version with which you can get good results from WinDbg. It is a current version built by a developer from the official source code with no official branding enabled. Such a current trunk version can be found under . Download that file and unzip it somewhere.
DebuggingFirst you have to start WinDbg via Start->Programs->Debugging Tools for Windows->WinDbg. Now open the firefox.exe executable you downloaded before via File->Open Executable... You should now see a text window with some output in it and a input field below it. Enter in the input field these lines
.sympath SRV*c:\symbols*http://www.mcsmurf.de/mozilla/ff-symbols/ .symfix+ c:\symbols .reload /f
Now wait for the symbols to download. This may take some time. Now run Firefox via Debug->Go and try to reproduce the crasher or hang you are seeing. Switch back to WinDbg and look if there is some new text in the WinDbg Command window saying "Access violation" or similar. If there is not, click on Debug->Break (most likely you have to do this when you want to debug a hang). You should now see a input field again, enter <tt>kp</tt> there, this will give you the so-called stacktrace. Now it might take a while until you get some output, it needs to download between 10 and 20MB from the internet. Wait until it is done, then mark the text in that window and copy it into your clipboard with Ctrl+C so you can paste the stacktrace as a bug comment if needed.