projects
/
fw
/
openocd
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Fix "unused variable" warnings (errors) detected with GCC 4.7.0 - dubious fixes
[fw/openocd]
/
BUGS
diff --git
a/BUGS
b/BUGS
index 0cb99ae63de3721d119541d9d7aade9b5525b11c..5e640e75830316880742dec01d9046facc8b8b06 100644
(file)
--- a/
BUGS
+++ b/
BUGS
@@
-1,4
+1,4
@@
-// This file is part of the Do
yx
gen Developer Manual
+// This file is part of the Do
xy
gen Developer Manual
/** @page bugs Bug Reporting
Please report bugs by subscribing to the OpenOCD mailing list and
/** @page bugs Bug Reporting
Please report bugs by subscribing to the OpenOCD mailing list and
@@
-6,6
+6,12
@@
posting a message with your report:
openocd-development@lists.berlios.de
openocd-development@lists.berlios.de
+Also, please check the Trac bug database to see if a ticket for
+the bug has already been opened. You might be asked to open
+such a ticket, or to update an existing ticket with more data.
+
+ https://sourceforge.net/apps/trac/openocd/
+
To minimize work for OpenOCD developers, you should try to include
all of the information listed below. If you feel that some of the
items below are unnecessary for a clear bug report, you may leave
To minimize work for OpenOCD developers, you should try to include
all of the information listed below. If you feel that some of the
items below are unnecessary for a clear bug report, you may leave
@@
-22,12
+28,12
@@
that may be important.
- If the report is for a regression:
- Include logs for both working and broken versions.
- Find the precise version that caused the regression by binary search.
- If the report is for a regression:
- Include logs for both working and broken versions.
- Find the precise version that caused the regression by binary search.
- You can use "git bisect" to expedite this binary search:
+ You can use "git bisect" to expedite this binary search:
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
If possible, please develop and attach a patch that helps to expose or
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
If possible, please develop and attach a patch that helps to expose or
-solve the reported problem. See the PATCHES
file for more
information
-
for
that process.
+solve the reported problem. See the PATCHES
.txt file for
information
+
about
that process.
Attach all files directly to your posting. The mailing list knows to
transform attachments to links, but attachments must be less than 300KB
Attach all files directly to your posting. The mailing list knows to
transform attachments to links, but attachments must be less than 300KB
@@
-36,7
+42,7
@@
in total.
@section bugscrashdump Obtaining Crash Backtraces
If OpenOCD is crashing, there are two very effective things you can do to
@section bugscrashdump Obtaining Crash Backtraces
If OpenOCD is crashing, there are two very effective things you can do to
-improve your chances of getting help on the development mailing list.
+improve your chances of getting help on the development mailing list.
Try to reproduce the problem using the dummy JTAG interface to allow other developers to replicate
your problem robustly and use GDB to get a trace:@par
Try to reproduce the problem using the dummy JTAG interface to allow other developers to replicate
your problem robustly and use GDB to get a trace:@par