From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 46403@debbugs.gnu.org
Subject: bug#46403: SIGINT ignored when using system*
Date: Sun, 02 May 2021 01:19:10 +0200 [thread overview]
Message-ID: <87wnsi59g1.fsf@gnu.org> (raw)
In-Reply-To: <87zh0dqr9l.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 09 Feb 2021 14:56:06 +0100")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> I execute commands in a loop and wish to be able to interrupt the loop
> with SIGINT. Here’s the first attempt:
>
> guile -c \
> '(for-each (lambda (n)
> (display n)
> (system* "sleep" "3"))
> (list 1 2 3 4))'
>
> At no point will this program be interrupted by SIGINT. Strace reveals
> that SIGINT is in fact received and the sleep is interrupted, but the
> wait is restarted immediately afterward.
‘system*’ explicitly ignores SIGINT:
--8<---------------cut here---------------start------------->8---
/* Make sure the child can't kill us (as per normal system call). */
scm_dynwind_sigaction (SIGINT,
scm_from_uintptr_t ((uintptr_t) SIG_IGN),
SCM_UNDEFINED);
--8<---------------cut here---------------end--------------->8---
Indeed, system(3) says:
During execution of the command, SIGCHLD will be blocked, and SIGINT
and SIGQUIT will be ignored, in the process that calls system().
(These signals will be handled according to their defaults inside the
child process that executes command.)
(I did some archaeology and found it has always been this way since Rob
introduced ‘system*’ in 0db17ef9abd59da51ebc30d90fb2dc482b02a4a1.)
> Is this by design?
I think so!
Ludo’.
prev parent reply other threads:[~2021-05-01 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 13:56 bug#46403: SIGINT ignored when using system* Ricardo Wurmus
2021-05-01 23:19 ` Ludovic Courtès [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnsi59g1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46403@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).