Debugging

Differences between revisions 10 and 11
Revision 10 as of 2012-05-21 16:01:56
Size: 2097
Editor: uusijani
Comment: restructuring, language
Revision 11 as of 2012-05-21 16:02:42
Size: 2102
Editor: uusijani
Comment: typo: just +like any
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
Debugging symbols come in packages that can be [[InstallingSoftware|installed just any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows: Debugging symbols come in packages that can be [[InstallingSoftware|installed just like any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows:

If Chromium crashes and you want to file a bug upstream, use their linux template. Always include the output from the following command:

$ dpkg -l | grep chromium-

You'll need to provide a backtrace. It can be produced using gdb, with the help of debugging symbols.

Getting a backtrace

Debugging symbols come in packages that can be installed just like any other software package in Ubuntu. The debugging symbols package for Chromium is called chromium-browser-dbg. Once you've installed it, open a terminal and proceed as follows:

$ chromium-browser --debug 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

If the backtrace shows lots of lines with question marks (such as "#5 0x083949e0 in ?? ()"), you're likely to need additional debugging symbols packages. To find out which libraries Chromium is loading, try:

$ ldd /usr/lib/chromium-browser/chromium-browser

Then look for corresponding -dbg or -dbgsym packages in the repositories.

Debugging child processes

Since Chromium normally spawns several processes (such as the sandbox and renderers), the backtrace from the browser process may not be useful (unless it is the main process that crashes). For catching backtraces from Chromium's child processes, you should run Chromium with --single-process:

$ chromium-browser --debug --single-process 2>&1 | tee gdb-chromium.txt

Then proceed as above with gdb.

Once you feel your backtrace file (gdb-chromium.txt) is sufficient, attach it to your bug report.


CategoryDebugging

Chromium/Debugging (last edited 2012-07-11 10:33:46 by mitya57)