Re: problem with GNU C
On Wed, Aug 01, 2001 at 03:24:16PM +0600, Ilya Teterin wrote:
>
> > Oh, that's easy then. The socket is marked writable because the other end
> > has closed. You receive a SIGPIPE because you're writing to a closed
> socket.
> > Are you checking the return codes from write?
>
> Hmm, are you believe, that "other end" (peer?) closes socket when code
> running on the one box, and not closes when it's running on another box, at
> the same network? And why peer terminates connection only when socket is
> nonblocking? It more likelly that select() marks socket as writeable before
> it is actually writeable, or the system closes nonblocking socket for
> another reason.
You are seriously suggesting that it's more likely that there is a bug in
the system than that you are just misunderstanding what is going on. Post an
strace of both programs, otherwise we're just wasting our time here.
--
Martijn van Oosterhout <kleptog@svana.org>
http://svana.org/kleptog/
> It would be nice if someone came up with a certification system that
> actually separated those who can barely regurgitate what they crammed over
> the last few weeks from those who command secret ninja networking powers.
Reply to: