aboutsummaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authoroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2008-05-19 07:29:45 +0000
committeroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2008-05-19 07:29:45 +0000
commitd487a11b929de7d2637812ab03f6fa0eceb2d5f8 (patch)
treea7c708784acb84fd4990ef5692b074501d8fe6ed /BUGS
parent96ca4401bd1c64a4b809b9241efc764bb72f037e (diff)
downloadriscv-openocd-d487a11b929de7d2637812ab03f6fa0eceb2d5f8.zip
riscv-openocd-d487a11b929de7d2637812ab03f6fa0eceb2d5f8.tar.gz
riscv-openocd-d487a11b929de7d2637812ab03f6fa0eceb2d5f8.tar.bz2
added stack trace.
git-svn-id: svn://svn.berlios.de/openocd/trunk@661 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS6
1 files changed, 6 insertions, 0 deletions
diff --git a/BUGS b/BUGS
index 3484c9a..5c9569c 100644
--- a/BUGS
+++ b/BUGS
@@ -22,6 +22,12 @@ 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.
+- If OpenOCD is crashing, you can use GDB to get a trace:
+
+gdb --args openocd ....
+(gdb) run
+(gdb) bt
+=> here a stack trace is dumped.
attach files directly to the posting. The mailing list knows to
transform attachments to links so you will not be bloating anyones