[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-dev] Re: SIGPIPE on ::writeNet
From: |
strk |
Subject: |
Re: [Gnash-dev] Re: SIGPIPE on ::writeNet |
Date: |
Wed, 19 Nov 2008 15:23:01 +0100 |
On Wed, Nov 19, 2008 at 07:16:24AM -0700, Rob Savoye wrote:
> strk wrote:
>
>
> > What's the policy about those kind of signals ?
> > It's triggered on write(2) instead of it returning -1.
> > Socket is set in NONBLOCKING mode.
> >
> > Program received signal SIGPIPE, Broken pipe.
>
> This is likely because Red5 has terminated the network connection.
Ok, but shouldn't RTMPClient handle it internally rather
then letting the signal reach the caller ?
It results in an abort here..
--strk;