qbittorrent crashed with SIGSEGV in libtorrent::entry::list()

[Joseph Becher]

Binary package hint: qbittorrent

It was just open

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: qbittorrent 2.6.9-2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 5c1ba3190c67a23ea091122972eb3be3
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Wed May 4 14:27:50 2011
ExecutablePath: /usr/bin/qbittorrent
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: qbittorrent
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x60d8ec <_ZNK10libtorrent5entry4listEv@plt>: jmp *0x1774(%ebx)
 PC (0x0060d8ec) ok
 source "*0x1774(%ebx)" ok
 SP (0xbff46ea8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: qbittorrent
StacktraceTop:
 libtorrent::entry::list () from /usr/lib/libtorrent-rasterbar.so.6
 int libtorrent::detail::bencode_recursive<std::back_insert_iterator<std::vector<char, std::allocator<char> > > >(std::back_insert_iterator<std::vector<char, std::allocator<char> > >&, libtorrent::entry const&) () from /usr/lib/libtorrent-rasterbar.so.6
 QBtSession::QBtSession() ()
 QBtSession::instance() ()
 MainWindow::closeEvent(QCloseEvent*) ()
Title: qbittorrent crashed with SIGSEGV in libtorrent::entry::list()
UpgradeStatus: Upgraded to natty on 2011-04-02 (31 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare www-data

[Apport retracing service (apport)]

StacktraceTop:
 libtorrent::entry::list () from /usr/lib/libtorrent-rasterbar.so.6
 libtorrent::detail::bencode_recursive<std::back_insert_iterator<std::vector<char> > > (out=..., e=...) at ../../include/libtorrent/bencode.hpp:190
 QBtSession::QBtSession() ()
 QBtSession::instance() ()
 MainWindow::closeEvent(QCloseEvent*) ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.