Seg faults in 1.1.14 due to handlers being called on closed fds

By sticking in some additional debugging lines, I was able to come up with
the following:

97/07/30 15:19:44| comm_select: FD 28 ready for writing
97/07/30 15:19:44| commHandleWrite: FD 28: state=0x35e3c0, off 0, sz 2663.
97/07/30 15:19:44| RWStateCallbackAndFree: FD 28 code=0 rwstate=0x35e3c0
97/07/30 15:19:44| comm_close: FD 28
97/07/30 15:19:44| RWStateCallbackAndFree: FD 28 code=-1 rwstate=0x0
97/07/30 15:19:44| commCallCloseHandlers: FD 28
97/07/30 15:19:44| commCallCloseHandlers: FD 28 calling handler=0x23e5c
97/07/30 15:19:44| commCallCloseHandlers: FD 28 calling handler=0x17398
97/07/30 15:19:44| commCallCloseHandlers: FD 28 complete
97/07/30 15:19:44| comm_close: FD 28 closed
97/07/30 15:19:44| commSetSelect: FD 28 WRITE handler=0xc09c data=0x130ff0
97/07/30 15:19:44| comm_select: FD 28 ready for writing

Program received signal SIGSEGV, Segmentation fault.
diskHandleWrite (fd=28, entry=0x0) at disk.c:291
disk.c:291: No such file or directory.
(gdb) where
#0 diskHandleWrite (fd=28, entry=0x0) at disk.c:291
#1 0xa3ab in comm_select (sec=1) at comm.c:1154
#2 0x1f116 in main (argc=3, argv=0xefbfda88) at main.c:702
(gdb)

I'm currently trying to figure out what's calling that commSetSelect
there.

        -Mike Pelletier.
Received on Wed Jul 30 1997 - 13:44:23 MDT