[Chicken-janitors] #486: Interrupting a tcp read operation causes a crash

[Chicken Trac]

#486: Interrupting a tcp read operation causes a crash
--------------------------------------------------+-------------------------
 Reporter:  zbigniew                              |       Owner:  felix
     Type:  defect                                |      Status:  new  
 Priority:  major                                 |   Milestone:  4.7.0
Component:  core libraries                        |     Version:  4.6.x
 Keywords:  tcp scheduler crash girl interrupted  |  
--------------------------------------------------+-------------------------
 In 4.6.4 at the interpreter, if I read from an open tcp port with no
 available data, and then interrupt the operation with Ctrl-C, the system
 will crash the next time I try to open a TCP connection.

 This happens with 4.6.4 from Dec 12 2010 and from Jan 21 2011.  It does
 NOT occur with 4.5.8.  I did not investigate further (because Felix will
 figure this out in 5 seconds), but I wonder if it happened during the
 safer-scheduler merge.

 If you prefer, I can git bisect this to track it down.

 {{{
 CHICKEN
 (c)2008-2010 The Chicken Team
 (c)2000-2007 Felix L. Winkelmann
 Version 4.6.4 (experimental)
 macosx-unix-gnu-x86 [ manyargs dload ptables ]
 compiled 2010-12-16 on amaranth.xorinia.dim (Darwin)

 ; loading /Users/jim/.csirc ...
 #;1> (use tcp posix)
 ; loading library tcp ...
 ; loading library posix ...
 #;2> (define-values (i o) (tcp-connect "3e8.org" 80))
 #;3> (read-string #f i)
   C-c C-c
 *** user interrupt ***
 #;3> (define-values (i o) (tcp-connect "3e8.org" 80))
 ##sys#unblock-threads-for-i/o: thread on fd-list has wrong FD

 Process scheme exited abnormally with code 70
 }}}

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/486>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.