From: Ryan Prior <rprior@protonmail.com>
To: Foo Chuan Wei <chuanwei.foo@hotmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Why does sh in the build environment ignore SIGINT and SIGQUIT?
Date: Sun, 22 May 2022 14:14:51 +0000 [thread overview]
Message-ID: <3Lw7OBQIW1WT7otx0UqOHHSducDQfScyqO2KP81NCHVUAmmmsGm9-DaGqGH4FKuCRcBi8vpDTydYEDu2Qk7hBo45CDERStJdavZipGwvmwI=@protonmail.com> (raw)
In-Reply-To: <PU1PR01MB2155A56B7FD179919DDB37C18DD59@PU1PR01MB2155.apcprd01.prod.exchangelabs.com>
------- Original Message -------
On Sunday, May 22nd, 2022 at 8:00 AM, Foo Chuan Wei <chuanwei.foo@hotmail.com> wrote:
> The shell in the environment where packages are built ignores SIGINT and
> SIGQUIT. If I add `(invoke "sh" "-c" "trap")` to a custom build phase
That executes a shell which traps and then immediately exits. By the next step of the build phase execution it's already gone. The shell isn't ignoring you - it's not running at all.
> The resulting [smlnj] executable seems to inherit the
> signal dispositions of the shell where the executable is built, with the
> result that CTRL-C is ignored at the sml REPL.
How would it know what some other process would do in response to a signal? Sounds extremely cursed.
next prev parent reply other threads:[~2022-05-22 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 8:00 Why does sh in the build environment ignore SIGINT and SIGQUIT? Foo Chuan Wei
2022-05-22 14:14 ` Ryan Prior [this message]
2022-05-23 3:14 ` Foo Chuan Wei
2022-05-24 6:25 ` Foo Chuan Wei
2022-05-24 23:28 ` Kaelyn
2022-05-30 15:20 ` 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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='3Lw7OBQIW1WT7otx0UqOHHSducDQfScyqO2KP81NCHVUAmmmsGm9-DaGqGH4FKuCRcBi8vpDTydYEDu2Qk7hBo45CDERStJdavZipGwvmwI=@protonmail.com' \
--to=rprior@protonmail.com \
--cc=chuanwei.foo@hotmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).