Decouple target_interrupt from all-stop/non-stop modes
authorPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:49:31 +0000 (16:49 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:56:39 +0000 (16:56 +0100)
commite42de8c7f8e7326d284f8b53f3bd6971fbf6e7b7
tree572a89f31b64944a5772acbdb8331e2cec9bde38
parenta149683b0c277279d892c9617233643188a34251
Decouple target_interrupt from all-stop/non-stop modes

In non-stop mode, "interrupt" results in a "stop with no signal",
while in all-stop mode, it results in a remote interrupt request /
stop with SIGINT.  This is currently implemented in both the Linux and
remote target backends.  Move it to the core code instead, making
target_interrupt specifically always about "Interrupting as if with
Ctrl-C", just like it is documented.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

* infcmd.c (interrupt_target_1): Call target_stop is in non-stop
mode.
* linux-nat.c (linux_nat_interrupt): Delete.
(linux_nat_add_target): Don't install linux_nat_interrupt.
* remote.c (remote_interrupt_ns): Change return type to void.
Throw error if interrupting the target is not supported.
(remote_interrupt): Don't call the remote_stop_ns/remote_stop_as.
gdb/ChangeLog
gdb/infcmd.c
gdb/linux-nat.c
gdb/remote.c
This page took 0.032971 seconds and 4 git commands to generate.