You are not logged in.

#1 2013-03-01 22:12:19

PotatoesMaster
Member
From: France
Registered: 2010-08-26
Posts: 54

Segmentation fault in OpenSSL's libcrypto.so on rtorrent startup

Hi archers,

When I start rtorrent, the curses UI shows up, and the program segfaults after some seconds.

Here is the console output:

 ~ $ rtorrent
Caught Segmentation fault, dumping stack:
0 rtorrent() [0x414449]
1 rtorrent() [0x450d4d]
2 /usr/lib/libc.so.6(+0x35340) [0x7f533b051340]
3 /usr/lib/libcrypto.so.1.0.0(BN_num_bits+0) [0x7f533a822270]
4 /usr/lib/libtorrent.so.14(+0xd486d) [0x7f533c4f186d]
5 /usr/lib/libtorrent.so.14(+0xb8eb8) [0x7f533c4d5eb8]
6 /usr/lib/libtorrent.so.14(+0xba41a) [0x7f533c4d741a]
7 /usr/lib/libtorrent.so.14(_ZN7torrent9PollEPoll7performEv+0xf5) [0x7f533c461505]
8 /usr/lib/libtorrent.so.14(_ZN7torrent9PollEPoll7do_pollEli+0x62) [0x7f533c461592]
9 /usr/lib/libtorrent.so.14(_ZN7torrent11thread_base10event_loopEPS0_+0x96) [0x7f533c498236]
10 rtorrent() [0x413997]
11 /usr/lib/libc.so.6(__libc_start_main+0xf5) [0x7f533b03da15]
12 rtorrent() [0x413f95]
zsh: abort (core dumped)  rtorrent

gdb's backtrace:

#0  0x00007ffff580f270 in BN_num_bits () from /usr/lib/libcrypto.so.1.0.0
#1  0x00007ffff74de86d in ?? () from /usr/lib/libtorrent.so.14
#2  0x00007ffff74c2eb8 in ?? () from /usr/lib/libtorrent.so.14
#3  0x00007ffff74c441a in ?? () from /usr/lib/libtorrent.so.14
#4  0x00007ffff744e505 in torrent::PollEPoll::perform() () from /usr/lib/libtorrent.so.14
#5  0x00007ffff744e592 in torrent::PollEPoll::do_poll(long, int) () from /usr/lib/libtorrent.so.14
#6  0x00007ffff7485236 in torrent::thread_base::event_loop(torrent::thread_base*) () from /usr/lib/libtorrent.so.14
#7  0x0000000000413997 in ?? ()
#8  0x00007ffff602aa15 in __libc_start_main () from /usr/lib/libc.so.6
#9  0x0000000000413f95 in ?? ()

And package versions:

curl           7.29.0-2
rtorrent-color 0.9.2-1 (also tried rtorrent 0.9.2-2: same error)
openssl        1.0.1.e-3
xmlrpc-c       1:1.33.01-1

I have quite a bit of torrents opened at the same time (around 80).
Since the error vanishes when these are removed, I tried to identify and remove only the faulty one. I removed a torrent coming from the Humble Bundle, but the problem reappeared later when I added some new torrents.

This thread describes a similar error but the solution is not suitable for my problem (there /dev/random and /dev/urandom were screwed up but mines are fine).

Any idea?

Offline

Board footer

Powered by FluxBB