Debugging

Differences between revisions 48 and 58 (spanning 10 versions)
⇤ ← Revision 48 as of 2008-12-03 02:37:16 →
Size: 1768
Editor: pool-71-117-238-148
Comment:
← Revision 58 as of 2009-12-15 16:26:22 → ⇥
Size: 1637
Editor: ip24-255-18-229
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<Include(Debugging/Header)>> <<Include(X/MenuBar)>>
Line 4: Line 4:
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 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.
Line 8: Line 6:
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.		 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.
Line 13: Line 8:
Even non-developers can help! The goal of this handbook is to give
folks a toolset for rendering these bugs easily solvable.		 == Contents ==
Line 16: Line 10:
== Contents: ==

   * I. [[X/Reporting]] - How to create good X bug reports
   * II. [[X/CommonErrors]] - Explanations for commonly seen error messages
   * III. [[X/Backtracing]] - How to collect a backtrace for an X crash
   * IV. [[X/Triaging]] - How to ensure new X bug reports have enough info to troubleshoot
   * V. [[X/Troubleshooting]] - How to analyze X bugs to make them solvable
   * VI. [[X/Quirks]] - Fixes for some common hardware-specific issues
   * VII. [[X/Upstreaming]] - Forwarding X bugs upstream		    I. [[X/Reporting]] - How to create good X bug reports
   I. [[X/Glossary]] - Explanations for commonly seen terms and error messages
   I. [[X/Backtracing]] - How to collect a backtrace for an X crash
   I. [[X/Triaging]] - How to ensure new X bug reports have enough info to troubleshoot
   I. [[X/Troubleshooting]] - How to analyze X bugs to make them solvable
   I. [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes
   I. [[X/Quirks]] - Fixes for some common hardware-specific issues
   I. [[X/Upstreaming]] - Forwarding X bugs upstream
Line 27: Line 20:
 * [[X/Bugs/ScreenModeChange]]
Line 29: Line 21:
 * [[https://help.ubuntu.com/community/FixVideoResolutionHowto|FixVideoResolutionHowto]] at help.ubuntu.com
Line 32: Line 23:
 * [[https://help.ubuntu.com/community/BinaryDriverHowto/ATI|BinaryDriverHowto]] - for installing fglrx or nvidia  * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia
Line 36: Line 27:
 * [[X/CommonErrors]]
 * [[X/DebuggingWithValgrind]]
 * [[X/ErrorMessages]]

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.

Contents

  1. X/Reporting - How to create good X bug reports

  2. X/Glossary - Explanations for commonly seen terms and error messages

  3. X/Backtracing - How to collect a backtrace for an X crash

  4. X/Triaging - How to ensure new X bug reports have enough info to troubleshoot

  5. X/Troubleshooting - How to analyze X bugs to make them solvable

  6. X/Bisecting - Using bisection techniques to solve regressions or backport fixes

  7. X/Quirks - Fixes for some common hardware-specific issues

  8. X/Upstreaming - Forwarding X bugs upstream

Other Resources

CategoryDebugging

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