SBCL dies when it has an USB device opened which gets unplugged and SLIME is open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Invalid
|
Undecided
|
Unassigned |
Bug Description
What I do:
I run SBCL with SLIME and I have a uno32 board (using the FT232R USB serial converter) plugged in.
I do
(defparameter out (open "/dev/ttyUSB0" :element-type 'base-char :direction :io :if-exists :append))
and I then unplug the USB device.
What happens:
SBCL dies (Lisp connection unexpectedly closed error in SLIME). This only happens when SLIME is used.
What I expected to happen:
SBCL not dying/replicates behavior when running SBCL from bash (nothing happens, write-char + force-output gives I/O error).
Test case:
1. Plug in USB device
2. Run SLIME in Emacs
3.. Open with OPEN as described above in SLIME
4. Unplug device
SBCL version: 1.3.10
uname -a:
Linux johan-ThinkPad-T520 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
*features*:
(:SWANK :QUICKLISP :QUICKLISP-
:ASDF-
:NON-BASE-
:ALIEN-CALLBACKS :ANSI-CL :ASH-RIGHT-VOPS :C-STACK-
:COMMON-LISP :COMPARE-
:FLOAT-EQL-VOPS :FP-AND-
:INLINE-CONSTANTS :INTEGER-EQL-VOP :LARGEFILE :LINKAGE-TABLE :LINUX
:LITTLE-ENDIAN :MEMORY-
:OS-PROVIDES-
:OS-PROVIDES-POLL :OS-PROVIDES-PUTWC :OS-PROVIDES-
:PACKAGE-
:READ-ONLY-TRAMPS :SB-CORE-
:SB-PACKAGE-LOCKS :SB-SIMD-PACK :SB-SOURCE-
:SB-UNICODE :SBCL :STACK-
:STACK-
:STACK-
:UNWIND-
Changed in sbcl: | |
status: | Incomplete → Invalid |
Can't reproduce.