Debugging

Differences between revisions 44 and 45
⇤ ← Revision 44 as of 2008-06-25 17:37:36 →
Size: 900
Editor: c-24-21-234-111
Comment:
← Revision 45 as of 2008-08-06 16:39:52 → ⇥
Size: 900
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
[[Include(Debugging/Header)]] <<Include(Debugging/Header)>>
Line 18: Line 18:
I. ["X/Reporting"] - How to properly report bugs in X I. [[X/Reporting]] - How to properly report bugs in X
Line 20: Line 20:
II. ["X/Backtracing"] - Getting gdb backtraces of X II. [[X/Backtracing]] - Getting gdb backtraces of X
Line 22: Line 22:
III. ["X/Triaging"] - Steps for processing newly reported bugs to make them ready for troubleshooting III. [[X/Triaging]] - Steps for processing newly reported bugs to make them ready for troubleshooting
Line 24: Line 24:
IV. ["X/Troubleshooting"] - Tips for analyzing and troubleshooting bugs IV. [[X/Troubleshooting]] - Tips for analyzing and troubleshooting bugs

Debugging Central

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

The X Windows System is a critical component in the Ubuntu operating system. X is not without its bugs, but fortunately debugging X issues is not rocket science.

The vast majority of Ubuntu X issues fall into one of several distinct categories, and based on the way they manifest, there are several different tactics that can be employed in a nearly paint-by-numbers fashion to isolate them.

Even non-developers can help! The goal of this handbook is to give folks a toolset for rendering these bugs easily solvable.

Contents:

I. X/Reporting - How to properly report bugs in X

II. X/Backtracing - Getting gdb backtraces of X

III. X/Triaging - Steps for processing newly reported bugs to make them ready for troubleshooting

IV. X/Troubleshooting - Tips for analyzing and troubleshooting bugs

X/Debugging (last edited 2016-01-10 22:13:08 by penalvch)