From: Christopher Baines <mail@cbaines.net>
To: 70144@debbugs.gnu.org
Subject: bug#70144: system* affects signal handlers
Date: Tue, 02 Apr 2024 15:22:57 +0100 [thread overview]
Message-ID: <87msqbrga2.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
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")
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next reply other threads:[~2024-04-02 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 14:22 Christopher Baines [this message]
2024-04-03 8:28 ` bug#70144: system* affects signal handlers Mikael Djurfeldt
2024-05-02 14:17 ` Ludovic Courtès
2024-05-05 16:41 ` Josselin Poiret via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2024-05-06 10:00 ` 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=87msqbrga2.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=70144@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).