From: Tomas Volf <~@wolfsden.cz>
To: 69730@debbugs.gnu.org
Subject: bug#69730: Segfault in (spawn) when passed wrong port
Date: Mon, 11 Mar 2024 12:10:31 +0100 [thread overview]
Message-ID: <Ze7mpzLyqXIdCb1l@ws> (raw)
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Greetings,
When I pass #f to spawn as a port, it just segfaults:
$ guile -c '(spawn "true" (list "") #:error #f)'
Segmentation fault
Ignoring the fact whether #f should be an accepted value (I think it would be
more elegant and portable then (open-output-file "/dev/null")), I would not
expect invalid value in an interpreted language to cause a segfault. If the
value is indeed invalid, it should throw an error.
Original report: https://emacs.ch/@kakafarm/112075808549752692
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-03-11 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 11:10 Tomas Volf [this message]
2024-05-06 9:27 ` bug#69730: Segfault in (spawn) when passed wrong 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=Ze7mpzLyqXIdCb1l@ws \
--to=~@wolfsden.cz \
--cc=69730@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).