Changes between Version 14 and Version 15 of Developer/Bug_Reporting


Ignore:
Timestamp:
Jan 6, 2016, 2:38:06 PM (4 years ago)
Author:
Ralph Holmes
Comment:

Fix links.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Bug_Reporting

    v14 v15  
    55Our preferred way of receiving bug reports is via the [http://devel.rtems.org RTEMS Trac] ticket system. If you have patches not specifically related to bugs or existing tickets, we prefer to use the [wiki:TBR/Website/RTEMSMailingLists Developer's Mailing List].
    66
    7 When you have checked that your report meets the following criteria, please submit it according to the generic instructions in [wiki:Developer/Bug_Reporting#Bugreportinginstructions Reporting a Bug].
     7When you have checked that your report meets the following criteria, please submit it according to the generic instructions in [#ReportingaBug Reporting a Bug].
    88
    99Please include in your bug report all of the following items:
     
    4444 *  When first developing a BSP, many users encounter an unexpected interrupt or exception immediately upon completion of RTEMS initialization. This occurs because interrupts are disabled during RTEMS initialization and are automatically initialized as part of switching to the first task. The interrupted user code will be in either _CPU_Context_switch or _Thread_Handler. This indicates that an interrupt source has not been properly initialized or masked.
    4545 *  Some users encounter a random reset during BSP initialization. This usually indicates that the board has a watchdog timer that is not being properly serviced during the BSP initialization.
     46
    4647== Reporting a Bug ==
    4748
     
    6162The [wiki:TracWorkflow Trac Ticket Workflow] details the workflow for RTEMS Tickets.
    6263
    63 Before you report a bug, please check the list of [wiki:#Non-Bugs #Non-Bugs] and a current development snapshot. If you want to report a bug with older versions of RTEMS, we strongly recommend upgrading to the current release first.
     64Before you report a bug, please check the list of [#NotRTEMSBugs non-bugs] and a current development snapshot. If you want to report a bug with older versions of RTEMS, we strongly recommend upgrading to the current release first.
    6465
    6566== Managing Bugs ==
     
    9293The state of a ticket is:
    9394
    94    '''open''':: The ticket has been filed and the responsible person(s) notified.
     95  '''open''':: The ticket has been filed and the responsible person(s) notified.
    9596  '''accepted''':: The assigned maintainer has verified that this is indeed a bug in RTEMS. Every once in a while, old reports will need to be rechecked, to find out whether the bug still exists. At that time, an indication should be left in the report who tested the bug and when.
    9697