added stack trace.

git-svn-id: svn://svn.berlios.de/openocd/trunk@661 b42882b7-edfa-0310-969c-e2dbd0fdcd60
2008-05-19 07:29:45 +00:00 · 2008-05-19 07:29:45 +00:00 · d487a11b92
parent 96ca4401bd
commit d487a11b92
1 changed files with 6 additions and 0 deletions
--- a/6
+++ b/6
@ -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