Version 5 (modified by pineappleskyes, on 01/01/16 at 06:04:20) (diff) |
---|
Please Read Before Creating a Ticket
Thank you for your interest in submitting a bug report. Before you get started please read through this short document to better help us address the issue you will be reporting.
- View the View Tickets Page
- Search for your problem. If this search isn't advanced enough for you, then try the Advanced Search.
- Review the RTEMS Bug Reporting page.
Required Information
It's not mandatory to fill in all information, but at the very least these fields are required:
- Summary
- Keep this short and concise to what your problem is.
- Description
- Include as many details of your problem as possible.
- Platform info (if applicable)
- Operating System name
- Version
- Any other relevant platform information.
- Type
- defect - A bug in the program or documentation.
- enhancement - A feature request in the software, or addition to the documentation.
- Version
- Set it to the version you're using, if it is the Git? version (not an official release) then set it to master.
- Test Cases
- Where possible, please attach or provide an in-line example that reproduces this problem. Try to make it the least possible amount of code to trigger the issue.
Attaching Files
If you have any external files such as screenshots or examples, please attach these as files to the ticket do not use external hosting, if you use external hosting then our historical record is broken when those files are no longer available.
Fields
Some fields should only be set by the developers as it's not always clear what they should be set to feel free to make your own choices.
Submitting a Ticket
In order to submit a ticket you must first register.
As long as you've read this page, then submit a ticket!.
Attachments (2)
- cfb_console.c (30.0 KB) - added by ostyche on 02/09/22 at 13:45:54.
- console-io.c (4.4 KB) - added by ostyche on 02/09/22 at 13:46:27.
Download all attachments as: .zip