Closing standard I/O streams ruins SBCL

Bug #585740 reported by Roman Marynchak on 2010-05-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Undecided
Unassigned

Bug Description

I know that it is unusual and funny, but anyway try both cases:

(close *standard-input*)

and

(close *standard-output*)

in REPL. On Win32 this leads to the more serious problems (infinite loop with printing VirtualAlloc info) than on Linux, but even on Linux the handling is worse than in CLISP (CLISP recovers from this by doing RESET).

Also, on Linux *standard-output* seems to be reopened after the abort, but *standard-input* is not.

This is low-priority, of course.

Regards,
Roman

Changed in sbcl:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers