Steps to reproduce:
- create Arguments sample
- set a line BP
- start debugger, it stops at BP
- stop debugger
- set 'console type' to 'Output Window'
- start debugger
Result: Debugger starts but does not stop at BP and does not finish at the same time. So it gets into 'unknown' state,
however it can be finished by clicking on 'Finish debug session' button.
Created attachment 71536 [details]
*** Issue 151005 has been marked as a duplicate of this issue. ***
added from issue #151005
The problem is that for some reason gdb on mac fails on
109-exec-run < /tmp/gdbFifo0.fifo > /tmp/gdbFifo1.fifo 2>&1
I was unable to reproduce it in standalone gdb.
*** Issue 151237 has been marked as a duplicate of this issue. ***
There is no safe fix for 6.5.
Workaround is to use external terminal.
This bug does not affect remote debugging on Linux and Solaris only on Mac.
fixed in the changeset:
not included into build 200812120201 but verified with a new org-...-debugger-gdb.jar
verified in build 200812150201
fix backported into release65_fixes branch
verified in patch2