Re: broken pipe
Re: broken pipe
- Subject: Re: broken pipe
- From: Greg Parker <email@hidden>
- Date: Thu, 19 Feb 2009 00:56:12 -0800
On Feb 18, 2009, at 8:38 PM, Rakesh Singhal wrote:
Thanks M and Shawn. I have already handler for SIGPIPE in which it is
doing nothing, just ignoring. When I get SIGPIPE, I am not getting any
error in write() call, does it mean my app is getting SIGPIPE due to
some other thing?
Shawn, I do not have any socket() in my app. I am communicating to
serial port through read() and write(), after setting some parameters.
If you catch the signal, or ignore it with SIG_IGN, then the failed
write() should return EPIPE.
Try this: set a breakpoint in your SIGPIPE signal handler and run your
app. When you get SIGPIPE and hit the breakpoint, look at the thread's
stack trace. The failing write() should be there.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden