[EMAIL PROTECTED] wrote:
99940 spamd-setup CALL close(0x3)
99940 spamd-setup RET close -1 errno 9 Bad file descriptor
99940 spamd-setup CALL pipe
99940 spamd-setup RET pipe 3
99940 spamd-setup CALL fork
99940 spamd-setup RET fork 99948/0x1866c
99940 spamd-setup CALL close(0x3)
99940 spamd-setup RET close 0
99940 spamd-setup CALL fcntl(0x4,0x3,0)
99940 spamd-setup RET fcntl 2
99940 spamd-setup CALL fstat(0x4,0xbfbff220)
99940 spamd-setup RET fstat 0
99940 spamd-setup CALL write(0x4,0x2830b000,0x4000)
99940 spamd-setup PSIG SIGPIPE SIG_DFL
is it of any use?
No, we'd need to see where fd 4 is being opened, but maybe that's a limitation
of ktrace. I could guess that that the pipe is between 3 and 4, so we'd have
to know what the spamd-setup child is doing. Could you run the trace with -i,
so that we can see why the child is closing the fd?
cheers
simon
