unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion <olivier.dion@polymtl.ca>
To: 73589@debbugs.gnu.org
Subject: bug#73589: system* does not honor SIGINT restoration in child
Date: Tue, 01 Oct 2024 16:51:03 -0400	[thread overview]
Message-ID: <87jzer7djc.fsf@laura> (raw)

Hi,

Given the following C program:
--8<---------------cut here---------------start------------->8---
#include <stdio.h>
#include <signal.h>

int main(void)
{
	struct sigaction act;

	sigaction(SIGINT, NULL, &act);

	printf("%p %p %p\n", act.sa_handler, SIG_IGN, SIG_DFL);
}
--8<---------------cut here---------------end--------------->8---

and its ouput from various executions:

  1) $ ./a.out => (nil) 0x1 (nil)
  2) $ guile -c '(system "./a.out")' => (nil) 0x1 (nil)
  3) $ guile -c '(system* "./a.out")' => 0x1 0x1 (nil)

We can see that 3) does not honor restoration of `SIGINT' to `SIG_DFL'
like `system(3)' does.  This seems to be because of the following
sigaction before the creation of the process:

--8<---------------cut here---------------start------------->8---
1697  scm_dynwind_sigaction (SIGINT,
1698                         scm_from_uintptr_t ((uintptr_t) SIG_IGN),
1699                         SCM_UNDEFINED);
1700 #ifdef SIGQUIT
1701  scm_dynwind_sigaction (SIGQUIT,
1702                         scm_from_uintptr_t ((uintptr_t) SIG_IGN),
1703                         SCM_UNDEFINED);
1704 #endif
1705
1706  err = piped_process (&pid, prog, args,
1707                       SCM_UNDEFINED, SCM_UNDEFINED);
--8<---------------cut here---------------end--------------->8---

From execve(2):

   POSIX.1 specifies that the dispositions of any signals that are
   ignored or set to the default are left unchanged.  POSIX.1 specifies
   one exception: if SIGCHLD is being ignored, then an implementation
   may leave the disposition unchanged or reset it to the default; Linux
   does the former.

Therefore, setting `SIG_IGN' for `SIGINT' before the fork/execve results
in ignoring the signals in the child, which is unexpected as a user of
`system(3)'.  The solution would be to restore `SIG_DFL' before
`execve(2)' if before the call to `system*' the action was not
`SIG_IGN'.

In the mean time, I have a solution that works for single-threaded
application:
--8<---------------cut here---------------start------------->8---
(define (system* . args)
  (let ((handler+flags (sigaction SIGINT)))
    (dynamic-wind
      (lambda ()
        (sigaction SIGINT SIG_IGN))
      (lambda ()
        (let ((cpid (primitive-fork)))
          (if (zero? cpid)
              (catch #t
                (lambda ()
                  (sigaction SIGINT SIG_DFL)
                  (apply execlp (car args) args))
                (lambda _
                  (primitive-exit EXIT_FAILURE)))
              (waitpid cpid))))
      (lambda ()
        (sigaction SIGINT
          (car handler+flags)
          (cdr handler+flags))))))
--8<---------------cut here---------------end--------------->8---

Thanks,
Olivier

-- 
Olivier Dion
oldiob.ca






             reply	other threads:[~2024-10-01 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 20:51 Olivier Dion [this message]
2024-10-20 18:58 ` bug#73589: system* does not honor SIGINT restoration in child Ludovic Courtès

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=87jzer7djc.fsf@laura \
    --to=olivier.dion@polymtl.ca \
    --cc=73589@debbugs.gnu.org \
    /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).