SIGPIPE crash

[anonymous]

Another crash under heavy load :/ Using 1038

Program received signal SIGPIPE, Broken pipe. 0xb7f467f2 in ?? () from /lib/ld-linux.so.2 (gdb) bt #0 0xb7f467f2 in ?? () from /lib/ld-linux.so.2 #1 0xb7bfa7d1 in send () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e45e91 in torrent::SocketStream::write_stream_throws (this=0x8aab130, buf=0xb4de81aa, length=11862) at socket_stream.h:94 #3 0xb7e510e0 in torrent::PeerConnectionBase::up_chunk (this=0x8aab128) at peer_connection_base.cc:647 #4 0xb7e559a8 in torrent::PeerConnectionLeech::event_write (this=0x8aab128) at peer_connection_leech.cc:558 #5 0xb7df095d in torrent::PollEPoll::perform (this=0x8125ca8) at poll_epoll.cc:138 #6 0x080bde04 in core::PollManagerEPoll::poll (this=0x8129ce0, timeout={m_time = 946632}) at poll_manager_epoll.cc:112 #7 0x0807cbe1 in main (argc=1, argv=0xbfef75d4) at main.cc:277

[anonymous]

I think this is because it's hitting a socket limit? Or maybe a buffer limit?

[rakshasa]

SIGPIPE is being set to ignore... must be something weird about your OS.

[anonymous]

It's a VM (openvz) if that's any help...

[anonymous]

Then it's probably a bug in that which lets SIGPIPE through even when it's supposed to be ignored. Not much rtorrent can do about it.