Standardize/ have consistency in the layout of How_to_Debug_<component> wiki pages.
"Jóhann B. Guðmundsson"
johannbg at hi.is
Fri Oct 9 08:25:18 UTC 2009
On 10/09/2009 01:58 AM, Christopher Beland wrote:
> On Thu, 2009-10-08 at 10:29 +0000, "Jóhann B. Guðmundsson" wrote:
>> Does not actually matter what we call these pages as long as they have
>> consistent naming and consistent layout.
> I'm pretty ambivalent as well, but if are agreed that consistency in
> naming is desired, we need to pick one system. My preferences are, in
> order from best to worst: "ComponentX Problems", "How to Debug
> ComponentX" and "Bug Info ComponentX". Perhaps someone can take a poll
> at the next meeting.
My preference are in the order from best to worst.. How to Debug ,
ComponentX Problems, Bug Info ComponentX
> I simplified and expanded the upper portions of the [[How to Debug
> Thunderbird]] page a bit; I hope the instruction to file extension bugs
> with extension authors is correct.
Yeah the simplification looks better . AFAIK the Thunderbird extensions
should be filed against Thunderbird then the maintainer ( or triager )
should move it to the appropriate place in upstream bugzilla if needed .
There is a reason I left out debugging Thunderbird extensions since it
requires you to setup different profile turning on couple knobs in
about:config extract jar file etc..
> The "Debugging Thunderbird" section could use some clarification. I
> assume that readers should only attempt to get a stack trace if they
> experience a crash?
I say users should always follow that procedure and file the gdb.txt
regardless if he stack traces or not then again this is something that
the maintainer needs to clarifies as what he wants on the report along
with how to handle broken extensions...
> The instructions for using gdb on the Thunderbird page are much more
> complicated than:
I would rather say that
is less informitive than the debugging section since it lacks the sample
output. The reason I put the sample output is to take out any mental
uncertainty ( or insecurity ) the low-knowledge reporter could be
dealing with. This is how you execute the command. This is the output if
you are doing it right.....
> Does the gdb logging described on the Thunderbird page get you anything
> more than a stack trace?
Try it break Thunderbird or Thunderbird extension and see for yourself...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 372 bytes
Desc: not available
More information about the fedora-test-list