[Ubuntu Wiki] Update of "MozillaTeam/Bugs" by micahg

Ubuntu Wiki noreply at ubuntu.com
Fri Jul 1 09:51:01 UTC 2011


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "MozillaTeam/Bugs" page has been changed by micahg:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=65&rev2=66

Comment:
Update wiki for Mozilla crash reporter and gdb debugging

  
  == Crashes ==
  
- === Using Apport to Submit a crash ===
+ === Submitting Crashes to Mozilla ===
  
- Follow instructions here [[https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport]]
+ The preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears.  To find your submitted crash data, go to about:crashes in the browser.  You can provide this crash id in the bug that you reported to Ubuntu. 
  
+ === Run Firefox in a Debugger ===
- === Attach Crash data to open bugs using apport ===
- 
- === Obtain a backtrace from an apport crash report (using gdb) ===
  
  Install the debugging symbols for firefox (and some other dbg packages like in above point):
  
@@ -63, +61 @@

       libc6-dbg
  }}}
  
- Copy and paste in a xterm the following command:
- 
- {{{
- TMPDIR=$(mktemp -d) 
- apport-unpack /var/crash/_usr_lib_firefox_firefox-bin.1000.crash $TMPDIR
- gdb -nx /usr/lib/firefox/firefox-bin -core $TMPDIR/CoreDump -ex 'backtrace full' -ex 'thread apply all backtrace full' -ex 'quit' 2>&1 | tee gdb.log
- rm -fr $TMPDIR
- }}}
- 
- That command will run gdb against the coredump file included in the crash report that was generated when firefox crashed. 
- 
- Upload the resulting gdb.log to launchpad.
- 
- One good thing to do is looking at the gdb output and search for missing dbg libraries or other warnings, install them and run again gdb. 
- 
- '''NOTE''' Please don't copy and paste the backtrace or text results to bug report if you can avoid it! We would prefer you attach them as text files - this way we can read them more easily and it won't make the page ridiculously long.
- 
- === Run Firefox in a Debugger ===
- 
- ==== Firefox-3.5 ====
- 
- If you had a crash, provide exact steps to reproduce the crash. If you cannot reproduce the crash, provide details of exactly what you were doing prior to the crash. Then, follow these steps: 
- 
-  1. Install debugging symbols by typing the following in a terminal (or install it with Adept or Synaptic): {{{
- # sudo apt-get install firefox-3.5-dbg \
-      xulrunner-1.9.1-dbg \
-      libgtk2.0-0-dbg \
-      libnss3-1d-dbg \
-      libnspr4-0d-dbg \
-      libpango1.0-0-dbg \
-      libcairo2-dbg \
-      libc6-dbg
- }}}
- 
  After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
- gdb /usr/lib/firefox-3*/firefox 2>&1 | tee /tmp/gdb-firefox.txt
- ... # someoutput
- (gdb) run
- ... # run and reproduce crash
- (gdb) bt full
- ... # full backtrace output
- (gdb) thread apply all backtrace full 
- ... # all threads full backtrace output
- (gdb) quit
- }}}
- 
- Now ~/tmp/gdb-firefox.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
- 
- 
- ==== Firefox-3.0 ====
- 
- Note the below instructions for this section do not work for Ubuntu Hardy users running Firefox3 betas. These users will receive "Couldn't find package firefox-dbg" because there is no dbg package created yet for Firefox3 beta users. As of now Firefox-3.0 users will need to use the following repos to get firefox-3.0-dbgsym and xulrunner-1.9-dbgsym: {{{
- deb http://ddebs.ubuntu.com jaunty main universe 
- deb http://ddebs.ubuntu.com jaunty-updates main universe
- deb http://ddebs.ubuntu.com jaunty-proposed main universe
- deb http://ddebs.ubuntu.com jaunty-security main universe
- }}}
- 
- If you had a crash, provide exact steps to reproduce the crash. If you cannot reproduce the crash, provide details of exactly what you were doing prior to the crash. Then, follow these steps: 
- 
-  1. Install debugging symbols by typing the following in a terminal (or install it with Adept or Synaptic): {{{
- # sudo apt-get install firefox-3.0-dbgsym \
-      xulrunner-1.9-dbgsym \
-      libgtk2.0-0-dbg \
-      libnss3-1d-dbgsym \
-      libnspr4-0d-dbg \
-      libpango1.0-0-dbg \
-      libcairo2-dbg \
-      libc6-dbg
- }}}
- 
- After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
- gdb /usr/lib/firefox-3*/firefox 2>&1 | tee /tmp/gdb-firefox.txt
- ... # someoutput
- (gdb) run
- ... # run and reproduce crash
- (gdb) bt full
- ... # full backtrace output
- (gdb) thread apply all backtrace full 
- ... # all threads full backtrace output
- (gdb) quit
- }}}
- 
- Now ~/tmp/gdb-firefox.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
- 
- ==== Firefox-2.0 ====
- 
-  1. After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
  firefox -g 2>&1 | tee ~/tmp/gdb-firefox.txt
  ... # some output
  (gdb) run



More information about the Ubuntu-bugsquad mailing list