gdb: Remove upstreamed SIGINT patch
The problem was fixed upstream, see: https://sourceware.org/bugzilla/show_bug.cgi?id=18945 https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=4c35c4c6a779c79e456b7a5311f74aafc9026bd5 Link: https://github.com/openwrt/openwrt/pull/16665 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
This commit is contained in:
parent
654983ea11
commit
c71e53bf9d
@ -1,35 +0,0 @@
|
|||||||
From 63df98fa78c8a6e12b40ebdc5c155838d2bf8b5f Mon Sep 17 00:00:00 2001
|
|
||||||
From: Khem Raj <raj.khem@gmail.com>
|
|
||||||
Date: Thu, 29 Nov 2018 18:00:23 -0800
|
|
||||||
Subject: [PATCH 11/11] gdbserver ctrl-c handling
|
|
||||||
|
|
||||||
This problem was created by the upstream commit 78708b7c8c
|
|
||||||
After applying the commit, it will send SIGINT to the process
|
|
||||||
group(-signal_pid).
|
|
||||||
But if we use gdbserver send SIGINT, and the attached process is not a
|
|
||||||
process
|
|
||||||
group leader, then the "kill (-signal_pid, SIGINT)" returns error and
|
|
||||||
fails to
|
|
||||||
interrupt the attached process.
|
|
||||||
|
|
||||||
Upstream-Status: Submitted
|
|
||||||
[https://sourceware.org/bugzilla/show_bug.cgi?id=18945]
|
|
||||||
|
|
||||||
Author: Josh Gao
|
|
||||||
Signed-off-by: Zhixiong Chi <zhixiong.chi@windriver.com>
|
|
||||||
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
||||||
---
|
|
||||||
gdbserver/linux-low.cc | 2 +-
|
|
||||||
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
||||||
|
|
||||||
--- a/gdbserver/linux-low.cc
|
|
||||||
+++ b/gdbserver/linux-low.cc
|
|
||||||
@@ -5525,7 +5525,7 @@ linux_process_target::request_interrupt
|
|
||||||
{
|
|
||||||
/* Send a SIGINT to the process group. This acts just like the user
|
|
||||||
typed a ^C on the controlling terminal. */
|
|
||||||
- int res = ::kill (-signal_pid, SIGINT);
|
|
||||||
+ int res = ::kill (signal_pid, SIGINT);
|
|
||||||
if (res == -1)
|
|
||||||
warning (_("Sending SIGINT to process group of pid %ld failed: %s"),
|
|
||||||
signal_pid, safe_strerror (errno));
|
|
Loading…
x
Reference in New Issue
Block a user