Debugging
⇤ ← Revision 1 as of 2009-05-22 23:37:42
1655
Comment:
|
1684
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
If chromium crashes and if you want to file a [[http://code.google.com/p/chromium/issues/entry|bug upstream]], you will need to provide a proper backtrace for your crash. | If chromium crashes and if you want to file a [[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|bug upstream]], you will need to provide a proper backtrace for your crash. |
Debugging Chromium crashes
If chromium crashes and if you want to file a bug upstream, you will need to provide a proper backtrace for your crash.
It could be accomplished using gdb and some debug packages.
If you know nothing about gdb, the generic instructions are available here: Backtraces with gdb
The debug package for chromium is called chromium-browser-dbg (it's big, ~120MB). It could be installed and removed like any other packages.
Note: you may need other debug packages if the backtrace shows lines like "#5 0x083949e0 in ?? ()". In that case, you need the corresponding -dbg or -dbgsym packages. Instructions about those are available in DebuggingProgramCrash
Once done, open a terminal and proceed as follow:
gdb /usr/lib/chromium-browser/chrome 2>&1 | tee gdb-chromium.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) run <arguments, if any>
do what you need to do to trigger the crash, then:
(gdb) backtrace (gdb) thread apply all backtrace (gdb) quit
Check the file gdb-chromium.txt to see if it contains symbols (as few "?? ()" as possible). If not, please locate and install the missing debug package(s) and retry.
Note: ldd /usr/lib/chromium-browser/chrome could give you a clue of which libs are loaded, and http://packages.ubuntu.com/ could tell you in which package they live.
Once you feel it's good enough, you may attach the file gdb-chromium.txt to your bug report.
Chromium/Debugging (last edited 2012-07-11 10:33:46 by mitya57)