This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] Decouple target_interrupt from all-stop/non-stop modes
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Tue, 12 Apr 2016 19:43:47 -0400
- Subject: [binutils-gdb] Decouple target_interrupt from all-stop/non-stop modes
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT e42de8c7f8e7326d284f8b53f3bd6971fbf6e7b7 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e42de8c7f8e7326d284f8b53f3bd6971fbf6e7b7
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.