Use 'event_ptid' instead of 'resume_ptid' on startup_inferior (fix for regression on my last commit)
Commit Message
Pedro pointed out a regression happening on gdb.mi/mi-exec-run.exp,
and as it turned out, this was a thinko when dealing with some events
on startup_inferior. Basically, one needs to pass 'event_ptid' to
target_mourn_inferior, but I mistakenly passed 'resume_ptid'.
This commit fixes it.
Built and regtested on BuildBot, now with fixed e-mail notifications!
gdb/ChangeLog:
2016-09-20 Sergio Durigan Junior <sergiodj@redhat.com>
* fork-inferior.c (startup_inferior): Pass 'event_ptid' instead of
'resume_ptid' to 'target_mourn_inferior'. Fix regression
introduced by my last commit.
---
gdb/ChangeLog | 6 ++++++
gdb/fork-child.c | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
Comments
On Tuesday, September 20 2016, Pedro Alves wrote:
> OK.
Thanks, pushed.
7d5adfe3118050243e85469ad891c7813e4db68a
@@ -1,3 +1,9 @@
+2016-09-20 Sergio Durigan Junior <sergiodj@redhat.com>
+
+ * fork-inferior.c (startup_inferior): Pass 'event_ptid' instead of
+ 'resume_ptid' to 'target_mourn_inferior'. Fix regression
+ introduced by my last commit.
+
2016-09-19 Pedro Alves <palves@redhat.com>
* common/gdb_locale.h [!ENABLE_NLS] (gettext, dgettext, dcgettext,
@@ -482,7 +482,7 @@ startup_inferior (int ntraps)
case TARGET_WAITKIND_SIGNALLED:
target_terminal_ours ();
- target_mourn_inferior (resume_ptid);
+ target_mourn_inferior (event_ptid);
error (_("During startup program terminated with signal %s, %s."),
gdb_signal_to_name (ws.value.sig),
gdb_signal_to_string (ws.value.sig));
@@ -490,7 +490,7 @@ startup_inferior (int ntraps)
case TARGET_WAITKIND_EXITED:
target_terminal_ours ();
- target_mourn_inferior (resume_ptid);
+ target_mourn_inferior (event_ptid);
if (ws.value.integer)
error (_("During startup program exited with code %d."),
ws.value.integer);