From: Pedro Alves <palves@redhat.com>
To: Jim Chen <nchen@mozilla.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [GDBServer] Send SIGINT using process group ID
Date: Wed, 18 May 2016 12:10:00 -0000 [thread overview]
Message-ID: <fed7cbcf-3561-aeca-1dba-841de62258c4@redhat.com> (raw)
In-Reply-To: <1463003507-13094-2-git-send-email-nchen@mozilla.com>
On 05/11/2016 10:51 PM, Jim Chen wrote:
> Hi,
>
> linux_request_interrupt is supposed to send SIGINT to the process group,
> but it passes the process ID to kill() instead of the process group ID,
> which may not be the same as the process ID.
> The patch calls getpgid
> first to get the process group ID.
>
> Patch tested on arm-linux.
Can you expand on the use case you see this happening on, please?
I can imagine some, but I'd like to hear it from you.
Some have expressed desire to _not_ send the SIGINT to the whole
process group, which may make sense when you're attached to a
process rather than having started it. IIRC, there's a bug filed in
bugzilla about this.
Looking at the code, not-sending-to-process-group-when-attached
is what native GNU/Linux does too (inflow.c:pass_signal).
Seems like "c&" -> "interrupt" doesn't consider "attach" either,
as inf-ptrace.c:inf_ptrace_interrupt sends the SIGINT
to the process, and like gdbserver, assumes the inferior's
PID is the process group id.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-05-18 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:54 [PATCH] Specify python2 or python3 as Python program name Jim Chen
2016-05-11 21:54 ` [PATCH] [GDBServer] Send SIGINT using process group ID Jim Chen
2016-05-18 12:10 ` Pedro Alves [this message]
2016-05-19 16:01 ` Jim Chen
2016-05-12 5:54 ` [PATCH] Specify python2 or python3 as Python program name Eli Zaretskii
2016-05-12 12:50 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fed7cbcf-3561-aeca-1dba-841de62258c4@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=nchen@mozilla.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).