X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=BUGS;h=0cb99ae63de3721d119541d9d7aade9b5525b11c;hp=ceb0356dda73566a6eec086b6c780408c00f3d57;hb=e5b0a69ba99f58991ebb5d07ad947592f09728f1;hpb=deda6ea50913b95deb536d5596037512584d13a7

diff --git a/BUGS b/BUGS
index ceb0356dda..0cb99ae63d 100644
--- a/BUGS
+++ b/BUGS
@@ -22,7 +22,8 @@ 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.
-    For example: if testing version 550 works but 600 fail, then try 575, etc.
+    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
 solve the reported problem.  See the PATCHES file for more information
@@ -34,8 +35,15 @@ in total.
 
 @section bugscrashdump Obtaining Crash Backtraces
 
-If OpenOCD is crashing, you can use GDB to get a trace:@par
+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. 
+
+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
 @code
+% OPENOCDSRC/configure --enable-dummy ...
+% openocd -f interface/dummy.cfg -f target/xxx.cfg
+=> SEGFAULT
 % gdb --args openocd ....
 (gdb) run
 (gdb) bt