wip on reporting bugs.
git-svn-id: svn://svn.berlios.de/openocd/trunk@602 b42882b7-edfa-0310-969c-e2dbd0fdcd60__archive__
parent
45d94f6af9
commit
1ad9179f3a
|
@ -0,0 +1,28 @@
|
|||
Please report bugs by posting a message to
|
||||
|
||||
openocd-development@lists.berlios.de.
|
||||
|
||||
To minimize work for OpenOCD developers, you can include
|
||||
all the information below. If you feel that some of the
|
||||
items below are unecessary for a clear bug report, you
|
||||
leave them out.
|
||||
|
||||
|
||||
- Target PCB/board description
|
||||
- Config scripts
|
||||
- OpenOCD command line
|
||||
- List of commands issued or GDB operations performed
|
||||
- Expected result
|
||||
- Actual result
|
||||
- debug_level 3 logs
|
||||
- If this is a regression, include logs for working and broken
|
||||
version
|
||||
- If this is a regression, please find out the precise version
|
||||
that caused the regression. This can be done via a binary
|
||||
search. E.g. if version 550 worked and 600 failed, then try
|
||||
575, etc.
|
||||
|
||||
|
||||
attach files directly to the posting. The mailing list knows to
|
||||
transform attachments to links so you will not be bloating anyones
|
||||
mail box. Keep attachments to <100kBytes.
|
Loading…
Reference in New Issue