Skip navigation.
Home
The QNX Community Portal

View topic - Signal 13 on a socket connection?

Signal 13 on a socket connection?

Read-only archive of qnx.qnx4 (General QNX4 Discussion Group) at inn.qnx.com

Signal 13 on a socket connection?

Postby 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
Kevin Miller
 

Re: Signal 13 on a socket connection?

Postby 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
Robert Craig
 

Re: Signal 13 on a socket connection?

Postby seanb » 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
seanb
QNX Master
 
Posts: 133
Joined: Fri Jul 28, 2006 5:36 pm


Return to qnx.qnx4

Who is online

Users browsing this forum: No registered users and 4 guests