From: Vijay Marupudi <vijaymarupudi@gatech.edu>
To: Maxime Devos <maximedevos@telenet.be>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: RE: Question about handling SIGINT properly in Guile
Date: Wed, 17 Apr 2024 10:28:31 -0400 [thread overview]
Message-ID: <877cgwgj1s.fsf@vijaymarupudi.com> (raw)
In-Reply-To: <87bk6ab0ip.fsf@vijaymarupudi.com>
Here's another simple reproduction, Guile's own webserver module
(use-modules (web server))
(define (handler request body)
(values '((content-type . (text/plain)))
"Hello, World!"))
(run-server handler)
It needs two SIGINTs to properly end the program. I think I'm encountering a bug rather than a misconception...
~ Vijay
prev parent reply other threads:[~2024-04-17 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 14:46 Question about handling SIGINT properly in Guile Vijay Marupudi
2024-04-13 16:46 ` Olivier Dion
2024-04-13 20:22 ` Vijay Marupudi
2024-04-14 22:50 ` Maxime Devos
2024-04-14 23:12 ` Maxime Devos
2024-04-16 0:43 ` Vijay Marupudi
2024-04-17 14:28 ` Vijay Marupudi [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=877cgwgj1s.fsf@vijaymarupudi.com \
--to=vijaymarupudi@gatech.edu \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
/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).