DebuggingGNOME

Differences between revisions 2 and 3
Revision 2 as of 2006-12-20 15:59:31
Size: 768
Editor: i59F75879
Comment:
Revision 3 as of 2007-03-06 11:55:56
Size: 1467
Editor: cF5A6BF51
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

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:


CategoryBugSquad CategoryDesktopTeam