If you file a Bug Report in Bugzilla about a crash of Firefox3 or Seamonkey2 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 from the source. The reason for this is that the crash Reporter only collects the half of the needed information, the other part is stored on the Server which collects the Crash Reports.
Run Firefox in the Firefox safemode before generating a stack trace to be sure that this crash is not caused by an addon !
How To get a crash ID with the Mozilla Crash Reporter
The Mozilla crash Reporter window should automatically come up after Mozilla crashed.
Be sure that you checked the "Tell Mozilla about the crash" checkbox and select Restart.
The Crash Reporter should now submit the crash report and Firefox should open again. Type "about:crashes" in the URL bar and press Enter. Firefox should open a list of all submitted crash reports. Copy 1-3 IDs 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 our crash Reporter on windows. You can see the installed Version if you type "about:plugins" in Firefox URL Bar.You can either disable the Flash Plugin in Firefox under Tools/Addons/Plugins
or you can install Flash 10 Beta from Adobe. Be warned, it's a beta with known problems on a some sites.
Alternative Ways to get a Stacktrace
If the Mozilla crash Reporter doesn't come up after a crash or if you use a Build form a Linux Distribution use this instructions :
You can also use WinDbg if you get a hang/freeze instead of a crash.
In that case use the commands "!analyze -v -hang".