aboutsummaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authoroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-07-27 14:46:49 +0000
committeroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-07-27 14:46:49 +0000
commite9b919fbc67a12f8825732f028b33c66e8321e11 (patch)
tree0417fa1367af0576075b3fd94c1813776152ca1d /BUGS
parente31e6a10dedd7680de231dcfdc700c695d5e4844 (diff)
downloadriscv-openocd-e9b919fbc67a12f8825732f028b33c66e8321e11.zip
riscv-openocd-e9b919fbc67a12f8825732f028b33c66e8321e11.tar.gz
riscv-openocd-e9b919fbc67a12f8825732f028b33c66e8321e11.tar.bz2
add "dummy" interface trick to the BUGS reporting suggestions
git-svn-id: svn://svn.berlios.de/openocd/trunk@2569 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS9
1 files changed, 8 insertions, 1 deletions
diff --git a/BUGS b/BUGS
index ceb0356..abf8f7a 100644
--- a/BUGS
+++ b/BUGS
@@ -34,8 +34,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