From Fedora Project Wiki
(add intro, bump header levels) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<!--{{header|<component>}}--> | <!--{{header|<component>}}--> | ||
= Identifying your problem area = | This page describes how to debug <component>. For general information on how to file a bug, should you need to do so, please see [[Bugs and feature requests]]. | ||
Checking the [[Bugs/Common|common bugs page]] or searching in [http://bugzilla.redhat.com bugzilla] will save you time if your problem has already been reported. | |||
== Identifying your problem area == | |||
Something that ensures that the component in question is at fault not some other thing.. | Something that ensures that the component in question is at fault not some other thing.. | ||
= Information to include in your report = | == Information to include in your report == | ||
{{Anchor|AllInfo}} | {{Anchor|AllInfo}} | ||
== All bug reports == | === All bug reports === | ||
Sample entry | Sample entry | ||
| Line 18: | Line 22: | ||
* A copy of the components log file {{filename|/path/to/<components_log_file>}} | * A copy of the components log file {{filename|/path/to/<components_log_file>}} | ||
== <Component> related problems == | === <Component> related problems === | ||
Sample entry | Sample entry | ||
| Line 26: | Line 30: | ||
{{Anchor|Debugging}} | {{Anchor|Debugging}} | ||
= Debugging | == Debugging <component> == | ||
As root install <components> debug package. | |||
<pre># debuginfo-install <component></pre> | |||
How to GDB component | |||
{{admon/note| Sample Note }} | |||
{{admon/tip| Sample Tip}} | |||
{{admon/warning| Sample Warning}} | |||
[[Category:Debugging]] [[Category:How to]] | [[Category:Debugging]] [[Category:How to]] | ||
Latest revision as of 16:25, 7 October 2009
This page describes how to debug <component>. For general information on how to file a bug, should you need to do so, please see Bugs and feature requests.
Checking the common bugs page or searching in bugzilla will save you time if your problem has already been reported.
Identifying your problem area
Something that ensures that the component in question is at fault not some other thing..
Information to include in your report
All bug reports
Sample entry
In all cases, the following should be mentioned and attached to your bug report:
- The exact command-line used.
- A copy of the components log file
/path/to/<components_log_file>
Sample entry
As well as the information from the 'All bug reports' section, include the following information:
Debugging <component>
As root install <components> debug package.
# debuginfo-install <component>
How to GDB component
Sample Note
Sample Tip
Sample Warning