unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 61073@debbugs.gnu.org
Subject: bug#61073: ‘spawn’ crashes when passed a non-file port
Date: Thu, 26 Jan 2023 09:30:25 +0100	[thread overview]
Message-ID: <874jsdsnoe.fsf@inria.fr> (raw)

Here’s an example:

--8<---------------cut here---------------start------------->8---
$ ./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
--8<---------------cut here---------------end--------------->8---

This is due to the careless use of ‘SCM_FPORT_FDES’ there.

Ludo’.





             reply	other threads:[~2023-01-26  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  8:30 Ludovic Courtès [this message]
2023-01-26  8:45 ` bug#61073: ‘spawn’ crashes when passed a non-file port 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=874jsdsnoe.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=61073@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).