[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#69730: Segfault in (spawn) when passed wrong port
From: |
Tomas Volf |
Subject: |
bug#69730: Segfault in (spawn) when passed wrong port |
Date: |
Mon, 11 Mar 2024 12:10:31 +0100 |
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.
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#69730: Segfault in (spawn) when passed wrong port,
Tomas Volf <=