BUGS

   1 Please report bugs by posting a message to
   2
   3 openocd-development@lists.berlios.de.
   4
   5 To minimize work for OpenOCD developers, you can include
   6 all the information below.  If you feel that some of the
   7 items below are unnecessary for a clear bug report, you
   8 leave them out.
   9
  10
  11 - Target PCB/board description
  12 - Config scripts
  13 - OpenOCD command line
  14 - List of commands issued or GDB operations performed
  15 - Expected result
  16 - Actual result
  17 - debug_level 3 logs
  18 - If this is a regression, include logs for working and broken
  19 version
  20 - If this is a regression, please find out the precise version
  21 that caused the regression. This can be done via a binary
  22 search. E.g. if version 550 worked and 600 failed, then try
  23 575, etc.
  24
  25 - If OpenOCD is crashing, you can use GDB to get a trace:
  26
  27 gdb --args openocd ....
  28 (gdb) run
  29 (gdb) bt
  30 => here a stack trace is dumped.
  31
  32 attach files directly to the posting. The mailing list knows to
  33 transform attachments to links so you will not be bloating anyones
  34 mail box. Keep attachments to <100kBytes.