[Gnash-dev] SIGPIPE on ::writeNet

[strk]

I'm still doing rtmpget work, and hit
a SIGPIPE signal on network::writeNet.

This is with red5 installed and command:

 utilities/rtmpget -n -vv rtmp://localhost:1935

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.
[Switching to Thread 0x7f6250c04710 (LWP 25511)]
0x00007f62500b5510 in __write_nocancel () from /lib/libpthread.so.0
(gdb) bt
#0  0x00007f62500b5510 in __write_nocancel () from /lib/libpthread.so.0
#1  0x00007f62507baa17 in gnash::Network::writeNet (this=0x7fff58c2cc48, fd=5, 
buffer=0x62ca60 "\002",
    nbytes=128, timeout=<value optimized out>) at network.cpp:931

--strk;

 ()   ASCII Ribbon Campaign
 /\   Keep it simple!