- 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.
If possible, please develop and attach a patch that helps to expose or
solve the reported problem. See the PATCHES file for more information
@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