SIGPIPE problems
SIGPIPE problems
- Subject: SIGPIPE problems
- From: Chilton Webb <email@hidden>
- Date: Fri, 15 Mar 2002 12:53:48 -0600
Greetings fellow tunnelrunners,
I was under the impression that you could ignore sigpipes and use the
returned error (epipe) from a write to perform some action (like stop
writing to that socket)
My code thus far does this...
signal(SIGPIPE,SIG_IGN);
/*then, later...*/
nwritten = write(fd, Zero, nleft);
Now, when the socket at fd breaks, I get a SIGPIPE error. I was under
the impression that the call to signal would force that error to be
ignored. I'm not making any other calls to signal (afaik), so what gives?
I'm running this in the Project Builder Debugger, so does that always
catch sigpipes regardless of if they're flagged to be ignored? If so,
that could account for this behavior. At this stage of development, the
project needs to stay in the debugger, so I can't easily test if it's
just the debugger catching it or not.
Any help will be rewarded with valuable cash prizes not to exceed 2
cents.
Thanks,
-Chilton
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.