FilingBugs

Differences between revisions 4 and 5
Revision 4 as of 2010-10-08 16:57:46
Size: 1347
Editor: lns-bzn-25-82-254-143-160
Comment:
Revision 5 as of 2010-11-15 11:36:39
Size: 2823
Editor: dsl-124-150-39-75
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== Natty ==
Line 8: Line 9:
== How to produce record a backtrace? == == Getting a backtrace ==

Ensure that you have the [[https://wiki.ubuntu.com/DebuggingProgramCrash#Hardy 8.04 and Newer|debugging symbols]] for the compiz, nux and unity packages. If you want compiz to spit out a backtrace when it crashes, you can grab the crashhandler plugin from [[http://git.compiz.org/compiz/plugins/crashhandler|git]] and enable that in ccsm.

Otherwise, from tty1 (Ctrl + Alt + F1)

{{{
$ DISPLAY=:0 gdb compiz
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mutter...(no debugging symbols found)...done.
(gdb) set args --replace ccp
(gdb) set logging file 'compiz.log'
(gdb) run

[ and when compiz crashes, do...]

(gdb) bt full

[ then CTRL-D or re-run compiz to continue working ]

(gdb) run
}}}

You can also get a valgrind trace by running {{{valgrind compiz --replace ccp &}}} in a terminal. This is a little bit slower to get because it runs compiz under emulation, but it does produce some output which isn't possible to get from gdb.

== Maverick ==

=== How to produce record a backtrace? ===

If you find an issue with Unity, here are some guidelines for filing bugs and providing details to the development team

Where to file bugs?

You should file bugs against Unity in Launchpad.

Natty

Getting a backtrace

Ensure that you have the debugging symbols for the compiz, nux and unity packages. If you want compiz to spit out a backtrace when it crashes, you can grab the crashhandler plugin from git and enable that in ccsm.

Otherwise, from tty1 (Ctrl + Alt + F1)

$ DISPLAY=:0 gdb compiz
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mutter...(no debugging symbols found)...done.
(gdb) set args --replace ccp
(gdb) set logging file 'compiz.log'
(gdb) run

[ and when compiz crashes, do...]

(gdb) bt full

[ then CTRL-D or re-run compiz to continue working ]

(gdb) run

You can also get a valgrind trace by running valgrind compiz --replace ccp & in a terminal. This is a little bit slower to get because it runs compiz under emulation, but it does produce some output which isn't possible to get from gdb.

Maverick

How to produce record a backtrace?

Ensure you have the debugging symbols for mutter and unity and unity places packages.

Then, from tty1 (Ctrl + Alt + F1)

$ DISPLAY=:0 gdb mutter
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mutter...(no debugging symbols found)...done.
(gdb) set args --replace
(gdb) set logging file 'mutter.log'
(gdb) run

[ and when mutter crashes, do...]

(gdb) bt full

[ then CTRL-D or re-run mutter to continue working ]

(gdb) run

Then, you should have a mutter.log file that you need to attach to the bug report.

Unity/FilingBugs (last edited 2023-12-04 16:43:22 by jbicha)