DebuggingGNOME

Differences between revisions 2 and 16 (spanning 14 versions)
Revision 2 as of 2006-12-20 15:59:31
Size: 768
Editor: i59F75879
Comment:
Revision 16 as of 2008-08-06 16:36:10
Size: 1821
Editor: localhost
Comment: converted to 1.6 markup
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:
== General == = Debugging Menus =
Line 19: Line 29:
 * [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]
If you should ever have to debug GNOME menus, you might want to use this
{{{
MENU_VERBOSE=1 <program>
}}}
Line 22: Line 34:
= 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 23: Line 56:
Go back to '''[:DebuggingProcedures]'''.[[BR]]
CategoryDesktopTeam[[BR]]
CategoryBugSquad
CategoryBugSquad CategoryDesktopTeam CategoryDebugging

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

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