DebuggingGNOME

Differences between revisions 1 and 15 (spanning 14 versions)
⇤ ← Revision 1 as of 2006-12-05 15:51:18 →
Size: 550
Editor: i59F70FA0
Comment:
← Revision 15 as of 2008-06-23 20:33:25 → ⇥
Size: 1813
Editor: c-24-21-234-111
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(Debugging/Header)]]
||<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 25:
There's also a useful information on how to run your program under gdb at the DebuggingProgramCrash page
Line 17: Line 27:
= Debugging Menus =

If you should ever have to debug GNOME menus, you might want to use this
{{{
MENU_VERBOSE=1 <program>
}}}

= Known bugs =

Description of known issues, how to recognise them and stock responses/actions.

'''Open'''
||<rowbgcolor="#eeeeee"> '''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]
 * DebuggingProcedures
 * DebuggingGconf
 * [https://wiki.ubuntu.com/DebuggingGNOMEApplets DebuggingGNOMEApplets]
 * [https://wiki.ubuntu.com/DebuggingGNOMEPowerManager DebuggingGNOMEPowerManager]
Line 18: Line 56:
Go back to '''[:DebuggingProcedures]'''.[[BR]]
CategoryDesktopTeam[[BR]]
CategoryBugSquad		 CategoryBugSquad CategoryDesktopTeam CategoryDebugging

Include(Debugging/Header)

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

There's also a useful information on how to run your program under gdb at the DebuggingProgramCrash page

Debugging Menus

If you should ever have to debug GNOME menus, you might want to use this 

MENU_VERBOSE=1 <program>

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Non-bugs

TBD.

Also see:

CategoryBugSquad CategoryDesktopTeam CategoryDebugging