From: "Ludovic Courtès" <ludo@gnu.org>
To: 61073-done@debbugs.gnu.org
Subject: bug#61073: ‘spawn’ crashes when passed a non-file port
Date: Thu, 26 Jan 2023 09:45:35 +0100 [thread overview]
Message-ID: <87y1ppr8eo.fsf@gnu.org> (raw)
In-Reply-To: <874jsdsnoe.fsf@inria.fr> ("Ludovic Courtès"'s message of "Thu, 26 Jan 2023 09:30:25 +0100")
Ludovic Courtès <ludo@gnu.org> skribis:
> Here’s an example:
>
> $ ./meta/guile
> GNU Guile 3.0.9
> Copyright (C) 1995-2023 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (with-error-to-port (%make-void-port "w") (lambda () (spawn "date" (list "date"))))
> Segmentation fault
>
> This is due to the careless use of ‘SCM_FPORT_FDES’ there.
Fixed in 5b42f8c154906584455a4989038406c88b723cb0.
Ludo’.
prev parent reply other threads:[~2023-01-26 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 8:30 bug#61073: ‘spawn’ crashes when passed a non-file port Ludovic Courtès
2023-01-26 8:45 ` Ludovic Courtès [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=87y1ppr8eo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=61073-done@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).