From: Sam S. <sd...@gn...> - 2009-12-10 14:56:47
|
Don Cohen wrote: > > Does any of this help? not really. unless you can get a reproducible test case, there is very little I can do. however, you can run under gdb and put a breakpoint in low_close_handle: break stream.d:4527 commands print fd continue end and gdb will print a message whenever it closes an FD. however, FDs are reused, so you need to also print it when it is created, i.e., break make_socket_stream commands print handle continue end note that this will only serve to test my conjecture that the socket is closed twice. if it turns out to be correct, we would still have to hunt down the bug, which might not be easy. a reproducible test case would help :-) however, this is not necessarily the case - my unix expertize is insufficient. I urge you to discuss this on a unix forum (e.g., http://groups.google.com/group/comp.unix.programmer/) and post the link to the thread (or, better yet, the summary thereof) here. > #<INPUT BUFFERED SOCKET-STREAM (UNSIGNED-BYTE 8) 0.0.0.0:5210> why is host = 0.0.0.0? is this normal? > Break 3 AP5[16]> (POSIX:ERRNO) I meant the C variable. clisp has already told you this is a ebadf |