GNU bug report logs - #70144
system* affects signal handlers

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#70144: closed (system* affects signal handlers)
Date: Mon, 06 May 2024 10:02:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 06 May 2024 12:00:34 +0200
with message-id <87msp3l0ot.fsf <at> gnu.org>
and subject line Re: bug#70144: system* affects signal handlers
has caused the debbugs.gnu.org bug report #70144,
regarding system* affects signal handlers
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
70144: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70144
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Christopher Baines <mail <at> cbaines.net>
To: bug-guile <at> gnu.org
Subject: system* affects signal handlers
Date: Tue, 02 Apr 2024 15:22:57 +0100

[Message part 3 (text/plain, inline)]

I've encountered a situation where signal handlers don't seem to
run. With the following program, sending it SIGINT won't trigger the
handler, however if you remove the system* call, then the handler will
run.

  (use-modules (ice-9 threads))

  (call-with-new-thread
   (lambda ()
     ;; Remove the following system* call to fix the handler
     (system* "echo" "foo")))

  (sigaction SIGINT
    (lambda (sig)
      (peek "SIGINT handler")
      (exit 1)))

  (for-each
   (lambda _
     (sleep 1))
   (iota 30))

  (display "normal exit\n")

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: Mikael Djurfeldt <mikael <at> djurfeldt.com>, 70144-done <at> debbugs.gnu.org,
 Christopher Baines <mail <at> cbaines.net>
Subject: Re: bug#70144: system* affects signal handlers
Date: Mon, 06 May 2024 12:00:34 +0200

Hi,

Josselin Poiret <dev <at> jpoiret.xyz> skribis:

> Yes, I believe this is all taken care of by our use of posix_spawn
> (which was the point in the first place :) ).

Yup!  I pushed the fix as 4ae33f76d6b33ea0bedfa36050d44c88d08c2823.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.