Use target_continue{,_no_signal} instead of target_resume
authorSergio Durigan Junior <sergiodj@redhat.com>
Thu, 25 Aug 2016 20:26:24 +0000 (16:26 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Thu, 1 Sep 2016 18:53:51 +0000 (14:53 -0400)
commit049a857091cff98371b5688140832a3cf767153c
treed9c21fa009e7cac0b35a1dfd8f655b8c90f5ccf8
parent424844864aa6f49c616b3bb74a0a5ba9bcb92e72
Use target_continue{,_no_signal} instead of target_resume

This commit implements a new function, target_continue, on top of the
target_resume function.  Then, it replaces all calls to target_resume
by calls to target_continue or to the already existing
target_continue_no_signal.

This is one of the (many) necessary steps needed to consolidate the
target interface between GDB and gdbserver.  In particular, I am
interested in the impact this change will have on the unification of
the fork_inferior function (which I have been working on).

Tested on the BuildBot, no regressions introduced.

gdb/gdbserver/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

* server.c (start_inferior): New variable 'ptid'.  Replace calls
to the_target->resume by target_continue{,_no_signal}, depending
on the case.
* target.c (target_stop_and_wait): Call target_continue_no_signal
instead of the_target->resume.
(target_continue): New function.

gdb/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

* fork-child.c (startup_inferior): Replace calls to target_resume
by target_continue{,_no_signal}, depending on the case.
* linux-nat.c (cleanup_target_stop): Call
target_continue_no_signal instead of target_resume.
* procfs.c (procfs_wait): Likewise.
* target.c (target_continue): New function.
* target/target.h (target_continue): New prototype.
gdb/ChangeLog
gdb/fork-child.c
gdb/gdbserver/ChangeLog
gdb/gdbserver/server.c
gdb/gdbserver/target.c
gdb/linux-nat.c
gdb/procfs.c
gdb/target.c
gdb/target/target.h