Oops, fixed bug introduced by previous commit (44f5e1c314b3)
We *MUST NOT* check for async support because at the time we
issue (say) `r` command, the real target is not yet connected,
therefore check for async would return `false` even if in fact
async is supported.
So, just run all execution commands in background mode
unconditionally.
--- a/VDBSimpleDebuggerConsoleApplication.st Mon Jan 28 23:41:53 2019 +0000
+++ b/VDBSimpleDebuggerConsoleApplication.st Tue Jan 29 09:58:21 2019 +0000
@@ -89,11 +89,10 @@
].
cmd := GDBCommand parse: aString.
- (cmd isCLICommand and:[debugger hasFeatureAsync]) ifTrue:[
- "/ If target supports async execution and if CLI command
- "/ is one of the execution commands, run the command in
- "/ background. This allows user to interrupt it, among
- "/ other things.
+ cmd isCLICommand ifTrue:[
+ "/ If CLI command is one of the execution commands, run
+ "/ the command in background. This allows user to interrupt
+ "/ it, among other things.
"/
"/ See GDB manual, Section 5.5.3 Background Execution
@@ -115,7 +114,7 @@
].
"Created: / 25-01-2019 / 12:12:39 / Jan Vrany <jan.vrany@fit.cvut.cz>"
- "Modified: / 28-01-2019 / 23:00:00 / Jan Vrany <jan.vrany@fit.cvut.cz>"
+ "Modified (format): / 29-01-2019 / 09:37:54 / Jan Vrany <jan.vrany@fit.cvut.cz>"
! !
!VDBSimpleDebuggerConsoleApplication methodsFor:'aspects'!