gdbserver: Fix exec stop reply reporting conditions
authorPedro Alves <palves@redhat.com>
Tue, 15 Sep 2015 16:38:05 +0000 (17:38 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 15 Sep 2015 16:38:07 +0000 (17:38 +0100)
gdb/gdbserver/ChangeLog:
2015-09-15  Pedro Alves  <palves@redhat.com>

* remote-utils.c (prepare_resume_reply) <TARGET_WAITKIND_EXECD>:
Check whether to report exec events instead of checking whether
multiprocess is enabled.

gdb/gdbserver/ChangeLog
gdb/gdbserver/remote-utils.c

index 6d6097f..5c0cbce 100644 (file)
@@ -1,5 +1,11 @@
 2015-09-15  Pedro Alves  <palves@redhat.com>
 
+       * remote-utils.c (prepare_resume_reply) <TARGET_WAITKIND_EXECD>:
+       Check whether to report exec events instead of checking whether
+       multiprocess is enabled.
+
+2015-09-15  Pedro Alves  <palves@redhat.com>
+
        PR remote/18965
        * remote-utils.c (prepare_resume_reply): Merge
        TARGET_WAITKIND_VFORK_DONE switch case with the
index 78fbfac..7cf66cc 100644 (file)
@@ -1142,7 +1142,7 @@ prepare_resume_reply (char *buf, ptid_t ptid,
 
            sprintf (buf, "T%02xvforkdone:;", signal);
          }
-       else if (status->kind == TARGET_WAITKIND_EXECD && multi_process)
+       else if (status->kind == TARGET_WAITKIND_EXECD && report_exec_events)
          {
            enum gdb_signal signal = GDB_SIGNAL_TRAP;
            const char *event = "exec";