[iolib-devel] regression after 6d63d32fb7f400e93066cb37a139a43dae4721c1

Attila Lendvai attila.lendvai at gmail.com
Wed May 26 09:08:32 UTC 2010


> I've seen that exact error. My example programs will produce it.
> Just start up ex6-server, connect with ex5a-client, type 'hello'
> at the client prompt, then 'quit'. The client hangs around forever
> while the server closed the connection.

anything new on this?

i've managed to reproduce the problem using the examples and iolib
version 5dfec183c4d57fa315d2b29c92d2b90045ea8eed (current head)

i've added some output printing to the client code as seen below.

CL-USER> (in-package :iolib.examples)
EXAMPLES> (make-thread 'run-ex6-server :name "ex6 server")

EXAMPLES> (run-ex5a-client)
Connected to server 127.0.0.1:9999 from my local connection at 127.0.0.1:42670!
alma
Writing to socket: "alma"
Flushing socket
Done

Writing to socket: ""
Flushing socket
Done
alma

Writing to socket: ""
Flushing socket
Done

quit
Writing to socket: "quit"
Flushing socket
Done

happy writing?!
Writing to socket: "happy writing?!"
Flushing socket
Done
quit


and in the inferior lisp buffer i see:

Accepted a client from 127.0.0.1:42670
Creating line-echoer for 127.0.0.1:42670
Read 127.0.0.1:42670: alma
Wrote 127.0.0.1:42670: alma
Read 127.0.0.1:42670:
Wrote 127.0.0.1:42670:
Read 127.0.0.1:42670:
Wrote 127.0.0.1:42670:
Read 127.0.0.1:42670: quit
Wrote 127.0.0.1:42670: quit
Client requested quit!
Closing connection to 127.0.0.1:42670

as you can see "happy writing?!" was written into a socket that has
been closed by the server at the previous "quit" line.

i'm not sure it's exactly the same issue as mine, but could be related.

-- 
 attila




More information about the iolib-devel mailing list