unofficial mirror of 
 help / color / mirror / Atom feed
* bug#69730: Segfault in (spawn) when passed wrong port
@ 2024-03-11 11:10 Tomas Volf
  0 siblings, 0 replies; only message in thread
From: Tomas Volf @ 2024-03-11 11:10 UTC (permalink / raw)
  To: 69730

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]


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:

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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-03-11 11:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-11 11:10 bug#69730: Segfault in (spawn) when passed wrong port Tomas Volf

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).