Changes between Version 2 and Version 3 of BugReporting

Timestamp:

12/20/07 11:12:08 (5 years ago)

Author:

gbooker

Comment:

--

BugReporting

@@ -1 +1 @@
 If you are going to submit a bug report, there are a few steps to follow.
  1. [http://appletv.nanopi.net/trac/search Search] for an existing tickets.  If you find one that matches your report, comment there (if you have something to add)
- 1. Examine the last part of the console.  On the AppleTV, you can execute {{{tail /Library/Logs/Console/501/console.log}}}.  On Leopard, open {{{/Applications/Utilities/Console.app}}}.
+ 1. Examine the last part of the console.  On the AppleTV, you can execute {{{tail /Library/Logs/Console/501/console.log}}}.  On Leopard, open {{{/Applications/Utilities/Console.app}}}.  This is important even if it crashed, because it may have thrown an exception earlier in the code which caused the crash.
  1. If the console says that a crash log was written, examine that file.  The console tells you the location of this file.
-   a. If this file says that that it crashed due to an uncaught exception, there is no reason to post it.
+   a. If this file says that that it crashed due to an uncaught exception, there is no reason to post it, just the info form the console
+ 1. Prune the information.
+   a. Console log information need only have data about exceptions, errors, and the like that came from Front Row (Finder on the AppleTV).
+   a. Crash logs need only the last log, from the last set of ***** to the end.
  1. Post the above information here.
-   a. Posting information looks best if it is enclosed in triple curly brackets, like the following:
+   a. Upload the file to a trac ticket (a new one if yours is not a duplicate, with the existing one if you found a ticket just like yours).
+   a. Alternatively, you can post the info in your comment.  Posting information looks best if it is enclosed in triple curly brackets, like the following:
 {{{
 {{{