Include project doxygen configuration with distribution tarballs.

[openocd.git] / BUGS

diff --git a/BUGS b/BUGS
index 3484c9a69f42f1a9be3184f29012fe75f37bc6ce..55a4d31f05ced3cc2d9ccc08522bbd637c58bab4 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -4,7 +4,7 @@ openocd-development@lists.berlios.de.
 
 To minimize work for OpenOCD developers, you can include
 all the information below.  If you feel that some of the
-items below are unecessary for a clear bug report, you
+items below are unnecessary for a clear bug report, you
 leave them out.
 
 
@@ -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