If you file a bug report in Bugzilla about a crash of Firefox 3 or Seamonkey 2 you should include a stacktrace (call stack) in your report. This Article describes how to use the Mozilla Crash Reporter to get a crash ID and alternative ways to create a stack trace.
You need a binary build from Mozilla.org. The crash reporter does not work if you use a build from a Linux distribution or if you compiled Firefox from the source code. The reason for this is that the crash reporter only collects one half of the needed information, the other part (the debug symbols) is stored on the Crash Report Server. The server puts the submitted crash Report and the symbols together to form a stack trace.
How To get a crash ID with the Mozilla Crash Reporter
The Mozilla crash reporter window should automatically come up after Mozilla crashes.
Be sure that you checked the "Tell Mozilla about the crash" checkbox and click the Restart button.
The crash reporter should now submit the crash report and Firefox should open again. Type "about:crashes" in the Firefox URL bar and press enter. Firefox should open a list of all submitted crash reports. Copy the IDs of the appropriate crashes to your Bugzilla bug report. Be sure that you don't copy an ID of an unrelated crash report.
What to do if the crash Reporter doesn't come up after a crash (Windows only)
The Flash plugin version 9 is known to break the crash reporter on Windows. You can find out what version of Flash you have installed by typing "about:plugins" in Firefox URL Bar. You can either disable the Flash plugin in Firefox by using the Add-ons manager, accessible in the Tools menu.
Alternatively, you can install Flash 10 Beta from Adobe. Be warned, it's a beta with known problems on some sites. However, it is compatible with the crash reporter.
Alternative ways to get a stacktrace
If the Mozilla crash reporter doesn't come up after a crash, or if you use a Linux build, use these instructions:
See the article Create a stacktrace with Windbg for information on how to do this.
You can also use WinDbg if you get a hang or freeze instead of a crash. In that case use the command:
!analyze -v -hang