projects
/
fw
/
openocd
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
96ca440
)
added stack trace.
author
oharboe
<oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Mon, 19 May 2008 07:29:45 +0000
(07:29 +0000)
committer
oharboe
<oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Mon, 19 May 2008 07:29:45 +0000
(07:29 +0000)
git-svn-id: svn://svn.berlios.de/openocd/trunk@661
b42882b7
-edfa-0310-969c-
e2dbd0fdcd60
BUGS
patch
|
blob
|
history
diff --git
a/BUGS
b/BUGS
index 3484c9a69f42f1a9be3184f29012fe75f37bc6ce..5c9569cb6b656d3d4cf77183d22c7a041f5a7af8 100644
(file)
--- 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