Signal 13 on a socket connection?

bridged with qnx.qnx4
Post Reply
Kevin Miller

Signal 13 on a socket connection?

Post by Kevin Miller » Mon Feb 11, 2008 10:49 pm

I have a task that terminated on a signal 13, "broken pipe". It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin

Robert Craig

Re: Signal 13 on a socket connection?

Post by Robert Craig » Mon Feb 11, 2008 10:55 pm

Hi Kevin:

If one end of a TCP socket is closed or gets killed and the other end
attempts to send to it, a broken pipe error should occur. You should
check and see if the associated connection on the other computer is
still alive.

Robert.



Kevin Miller wrote:
I have a task that terminated on a signal 13, "broken pipe". It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin

Sean Boudreau

Re: Signal 13 on a socket connection?

Post by Sean Boudreau » Tue Feb 12, 2008 12:22 pm

If you set signal(SIGPIPE, SIG_IGN); the send() / write()
will fail with -1 and errno EPIPE.

-seanb

Robert Craig <rcraig_at_qnx@nowhere.com> wrote:
Hi Kevin:

If one end of a TCP socket is closed or gets killed and the other end
attempts to send to it, a broken pipe error should occur. You should
check and see if the associated connection on the other computer is
still alive.

Robert.



Kevin Miller wrote:
I have a task that terminated on a signal 13, "broken pipe". It did not
have a pipe open, but it was using a socket connection to another
computer on the LAN. Any idea what this would mean?

Thanks,

Kevin

Post Reply

Return to “qnx.qnx4”