Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 5 and Version 6 of HowToFileABug


Ignore:
Timestamp:
2010-07-27T20:57:30Z (9 years ago)
Author:
Jakub Jermář
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • HowToFileABug

    v5 v6  
    33As in any other complex software system, there will inevitably be bugs in the HelenOS source code (unless we can formally prove the opposite). It is therefore essential for people who run into them to make sure the bug is actually known to the developers and that all potentially relevant information that can help to root-cause the bug is available. This is best achieved by filing a ticket in our bug tracking database.
    44
    5 Writing bug reports is by far not that trivial as it may initially seem. Quite the contrary. Writing really good bug reports takes some effort and needs some practice, but the reward is high.  The ticket owner can then focus on solving the bug itself rather than figuring out all the information and circumstances that lead to the it. Below follows a list of tips for filing the most useful bug reports.
     5Writing bug reports is by far not that trivial as it may initially seem. Quite the contrary. Writing really good bug reports takes some effort and needs some practice, but the reward is high.  The ticket owner can then focus on solving the bug itself rather than figuring out all the information and circumstances that lead to it. Below follows a list of tips for filing the most useful bug reports.
    66
    77  * Make sure the bug is not a duplicate of some other bug
     
    1212  * Avoid creating multi-tickets
    1313    * '''bad''': ''Fix problem XYZ on amd64, arm32, ia32, ia64, mips32, ppc32 and sparc64''
    14     * Instead, consider filing separate tickets for all of the above architectures. This will make it easier to track progress on each architecture separately.
     14    * Instead, consider filing separate tickets for all of the above architectures. This will make it easier to track progress on each architecture separately
    1515  * Categorize the new bug using fitting ```Type```, ```Component``` and ```Version``` fields
    1616  * In the first comment section, provide a concise and complete problem statement
     
    2424      * number of processors
    2525      * name and version of the simulator/virtualizer, if the target system is a simulated machine
    26     * Provide reasonable details about HelenOS configurations
     26    * Provide reasonable details about HelenOS configuration
    2727      * consider attaching Makefile.config from the root of the HelenOS tree
    2828    * If there is a stack trace associated with the bug, paste it into the bug report
    2929      * In case there is a core dump generated for a crashing task, compress it and attach it to the ticket
    30       * Alternatively, attach the compressed binary itself (kernel.raw or the respective uspace binary). Note that attaching .disasm files is problematic as these files are usually much bigger than the respective binaries themselves (even when compressed).
    31     * If there are some terminal or console messages of interest such as warnings or errors, mention those in the bug report.
     30      * Alternatively, attach the compressed binary itself (kernel.raw or the respective uspace binary). Note that attaching .disasm files is problematic as these files are usually much bigger than the respective binaries themselves (even when compressed)
     31    * If there are some terminal or console messages of interest such as warnings or errors, mention those in the bug report