From: oharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Date: Mon, 19 May 2008 07:29:45 +0000 (+0000)
Subject: added stack trace.
X-Git-Tag: v0.1.0~628
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=d487a11b929de7d2637812ab03f6fa0eceb2d5f8;p=openocd

added stack trace.

git-svn-id: svn://svn.berlios.de/openocd/trunk@661 b42882b7-edfa-0310-969c-e2dbd0fdcd60
---

diff --git a/BUGS b/BUGS
index 3484c9a6..5c9569cb 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