How to get a stacktrace for a bug report

  • Revision slug: How_to_get_a_stacktrace_for_a_bug_report
  • Revision title: How to get a stacktrace for a bug report
  • Revision id: 100527
  • Created:
  • Creator: mversen
  • Is current revision? No
  • Comment 1 words added, 1 words removed

Revision Content

Introduction

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.

Requirements

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.

reporter.jpg

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.

crashlist.jpg

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

addons.jpg

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 :

Windows

 Create a stacktrace with Windbg

 You can also use WinDbg if you get a hang/freeze instead of a crash.
  In that case use the commands "!analyze -v -hang".

Linux

Revision Source

<h2>Introduction</h2>
<p>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.</p>
<h2>Requirements</h2>
<p>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.</p>
<p>Run Firefox in the <a class="external" href="http://support.mozilla.com/en-US/kb/Safe+Mode" title="http://support.mozilla.com/en-US/kb/Safe+Mode">Firefox safemode</a> before generating a stack trace to be sure that this crash is not caused by an addon !</p>
<h3>How To get a crash ID with the Mozilla Crash Reporter</h3>
<p>The Mozilla crash Reporter window should automatically come up after Mozilla crashed. <br>
Be sure that you checked the "Tell Mozilla about the crash" checkbox and select Restart.</p>
<p><img alt="reporter.jpg" class="internal default" src="/@api/deki/files/2854/=reporter.jpg?size=webview" style="width: 300px; height: 307px;"></p>
<p>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.</p>
<p><img alt="crashlist.jpg" class="internal default" src="/@api/deki/files/2855/=crashlist.jpg?size=webview" style="width: 450px; height: 403px;"></p>
<h4>What to do if the crash Reporter doesn't come up after a crash (Windows only)</h4>
<p>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</p>
<p><img alt="addons.jpg" class="internal default" src="/@api/deki/files/2856/=addons.jpg?size=webview" style="width: 400px; height: 292px;"></p>
<p>or you can install <a class="external" href="http://labs.adobe.com/technologies/flashplayer10/" title="http://labs.adobe.com/technologies/flashplayer10/">Flash 10 Beta from Adobe</a>. Be warned, it's a beta with known problems on a some sites.</p>
<h3>Alternative ways to get a Stacktrace</h3>
<p>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 :</p>
<h5>Windows</h5>
<p> <a class="internal" href="/en/How_to_get_a_stacktrace_with_WinDbg" title="En/How to get a stacktrace with WinDbg">Create a stacktrace with Windbg</a></p>
<p> You can also use WinDbg if you get a hang/freeze instead of a crash.<br>
  In that case use the commands "!analyze -v -hang".</p>
<h5>Linux</h5>
<ul> <li> <p>Ubuntu :   I<a class="link-https" href="https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29" title="https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain a backtrace from an apport crash report (using gdb)">nstructions from the Ubuntu Team</a></p> </li> <li> Suse : <a class="external" href="http://en.opensuse.org/Bugs:An_application_crashed" title="http://en.opensuse.org/Bugs:An_application_crashed">Instructions from SuSe</a>  Note:  to run firefox under a debugger you should use: "./run-mozilla.sh -g -d gdb ./firefox-bin" not "gdb ./firefox"</li>
</ul>
Revert to this revision