DebuggingGNOME
Size: 768
Comment:
|
Size: 1467
Comment: new template form
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| = Introduction = TBD. = Debugging procedure = |
|
Line 16: | Line 24: |
= Known bugs = | |
Line 17: | Line 26: |
== General == | Description of known issues, how to recognise them and stock responses/actions. '''Open''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || '''Closed''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || = Non-bugs = TBD. ------ '''Also see:''' |
Line 21: | Line 45: |
* DebuggingProcedures | |
Line 23: | Line 48: |
Go back to '''[:DebuggingProcedures]'''.[[BR]] CategoryDesktopTeam[[BR]] CategoryBugSquad |
CategoryBugSquad CategoryDesktopTeam |
ContentsBRTableOfContents |
Introduction
TBD.
Debugging procedure
In Ubuntu we have disabled the feature that makes applications crash on critical warnings. To debug problems it's sometimes good to have this happening.
This will make it crash:
G_DEBUG=fatal_criticals <program>
If you additionally run the program under gdb or valgrind, it will help you to figure out, what led to the critical warning.
This will make a program stop on warnings:
<program> --g-fatal-warnings
Known bugs
Description of known issues, how to recognise them and stock responses/actions.
Open
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Closed
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Non-bugs
TBD.
Also see:
[http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines Some useful information from the GNOME team]
[http://www.gnome.org/projects/evolution/bugs.shtml More info on evolution]