rtems/rtems-source-builder
1
0
Fork 0
mirror of https://git.rtems.org/rtems-source-builder synced 2024-10-09 07:15:10 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc: Improve the section on reporting errors.

Browse Source
This commit is contained in:
Chris Johns 2013-08-27 08:02:54 +10:00
parent 5e536f822d
commit 174d296ffb
1 changed files with 17 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/source-builder.txt
View File

@ -60,6 +60,9 @@ assume the build sets and configuration files you are using have been created
by developers who do. If you have a problem please ask on the RTEMS Users
mailing list.
IMPORTANT: If you have a problem please see <<_bugs,the reporting bugs>>
section.
Quick Start
-----------
@ -583,6 +586,7 @@ own tool set that you install under your home directory. Avoiding installing
any extra packages as a super user is always helpful in maintaining a secure
computing environment.
[[_bugs]]
Bugs, Crashes, and Build Failures
---------------------------------
@ -594,12 +598,19 @@ https://www.rtems.org/bugzilla/
or via email on the RTEMS Users list.
Please include the git hash you are running, the host details with the output
of the +uname -a+ command. If there is a crash please cut and paste the Python
backtrace into the bug report. If the tools fail to build please locate the
first error in the log file. This can be difficult to find on hosts with many
cores so it sometimes pays to run the command with the +--jobs=none+ option to
get a log that is correctly sequenced.
Please include the:
. Command line,
. The git hash,
. Host details with the output of the +uname -a+ command,
. If you have made any modifications.
If there is a crash please cut and paste the Python backtrace into the bug
report. If the tools fail to build please locate the first error in the log
file. This can be difficult to find on hosts with many cores so it sometimes
pays to run the command with the +--jobs=none+ option to get a log that is
correctly sequenced. If searching the log file seach for +error:+ and the error
should be just above it.
Configuration
-------------