Using this simple test program: int main() { for (;;); return 0; } And trying these commands: $ gdb -nx -i mi a.out -gdb-set mi-async on -exec-run -exec-interrupt --all <--- It doesn't work, even though it should since we are in mi-async on mode. I traced the root of the problem to this line: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/mi/mi-main.c;h=7412f7d8a553ca6739da1480c2e84572f38a8e78;hb=HEAD#l493 At this point, the linux-native run target is not pushed yet. mi_async_p ends up calling tdefault_can_async, which returns false, so we don't execute asynchronously.
Created attachment 8164 [details] Test case .exp
Created attachment 8165 [details] Test case .c
I added a test case that I made quickly (copied from mi-async.exp). It passes when I replace the return 0 in tdefault_can_async_p by return 1. It's obviously not the right solution, but I think it shows what the behaviour should be on linux-nat.
-exec-run should probably call find_run_target() and use that target to check for async support, like infcmd.c:run_command_1 does.
I'm very surprised I didn't notice this before. Probably shows some deficiency in the testing we do. We always test eclipse with a default breakpoint at "main" which interrupts the execution and then the asynchronous stuff starts to work. But if I start a non-stop session without any breakpoints (so the execution does not stop on its own), the session is borked; can't set breakpoints, can't interrupt, it doesn't even display completely.
The master branch has been updated by Simon Marchi <simark@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70 commit 61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70 Author: Simon Marchi <simon.marchi@ericsson.com> Date: Tue May 17 16:44:57 2016 -0400 Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) When doing -exec-run on a freshly started GDB, the only target on the target stack at the time the dummy one. When mi_async_p is called to know whether the run should be async, it queries whether the current target (dummy) supports async, and the answer is no. The fix is to make the code query the target that will be used for the run, which is not necessarily the current target. No regressions in the gdb.mi directory using the unix, native-gdbserver and native-extended-gdbserver boards. The test doesn't pass when forcing maint set target-async off, obviously, since it makes mi-async have no effect. It doesn't seem like other tests are checking for that eventuality, so I didn't in the new test. gdb/ChangeLog: * mi/mi-main.c (run_one_inferior): Use run target to determine whether to run async or not. (mi_cmd_exec_run): Likewise. gdb/testsuite/ChangeLog: * gdb.mi/mi-async-run.exp: New file. * gdb.mi/mi-async-run.c: New file.
The gdb-7.11-branch branch has been updated by Simon Marchi <simark@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b5f0db46b3057bcb64243e7da0943717abd6459b commit b5f0db46b3057bcb64243e7da0943717abd6459b Author: Simon Marchi <simon.marchi@ericsson.com> Date: Tue May 17 16:44:57 2016 -0400 Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) When doing -exec-run on a freshly started GDB, the only target on the target stack at the time the dummy one. When mi_async_p is called to know whether the run should be async, it queries whether the current target (dummy) supports async, and the answer is no. The fix is to make the code query the target that will be used for the run, which is not necessarily the current target. No regressions in the gdb.mi directory using the unix, native-gdbserver and native-extended-gdbserver boards. The test doesn't pass when forcing maint set target-async off, obviously, since it makes mi-async have no effect. It doesn't seem like other tests are checking for that eventuality, so I didn't in the new test. gdb/ChangeLog: * mi/mi-main.c (run_one_inferior): Use run target to determine whether to run async or not. (mi_cmd_exec_run): Likewise. gdb/testsuite/ChangeLog: * gdb.mi/mi-async-run.exp: New file. * gdb.mi/mi-async-run.c: New file.
Patch is pushed.