Bug 215627 - Unexpected crash coming from the nothing
Summary: Unexpected crash coming from the nothing
Status: RESOLVED DUPLICATE of bug 214103
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-22 02:23 UTC by Manuel
Modified: 2009-11-22 10:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel 2009-11-22 02:23:16 UTC
Application that crashed: ktorrent
Version of the application: 3.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.27-14-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
[Current thread is 0 (LWP 7608)]

Thread 8 (Thread 0xb36ffb90 (LWP 7642)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb660a7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7fcc731 in dht::RPCServerThread::run () from /usr/lib/libbtcore.so.12
#3  0xb71d3132 in QThreadPrivate::start (arg=0xa1ad310) at thread/qthread_unix.cpp:188
#4  0xb5d0c4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb661249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 7 (Thread 0xb40d3b90 (LWP 8008)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb5d10412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6621344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xa8ea1ae3 in ?? () from /usr/lib/libxine.so.1

Thread 6 (Thread 0xb0f39b90 (LWP 8009)):
#0  0xb66214d1 in pthread_mutex_unlock () from /lib/tls/i686/cmov/libc.so.6
#1  0xb5c4e9b4 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#2  0xb5c4edda in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb5c4f268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4  0xb72f3317 in QEventDispatcherGlib::processEvents (this=0xc261120, flags={i = -1326214552}) at kernel/qeventdispatcher_glib.cpp:329
#5  0xb72c61fa in QEventLoop::processEvents (this=0xb0f392e0, flags={i = -1326214488}) at kernel/qeventloop.cpp:149
#6  0xb72c6642 in QEventLoop::exec (this=0xb0f392e0, flags={i = -1326214424}) at kernel/qeventloop.cpp:201
#7  0xb71cfe19 in QThread::exec (this=0xc260010) at thread/qthread.cpp:487
#8  0xa8eef20a in ?? () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#9  0xb71d3132 in QThreadPrivate::start (arg=0xc260010) at thread/qthread_unix.cpp:188
#10 0xb5d0c4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb661249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 5 (Thread 0xb273cb90 (LWP 8010)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb5d100e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb66212ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xa8eb2d8e in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 0xa5611b90 (LWP 8020)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb5d10412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6621344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb71d2b29 in thread_sleep (ti=0xa56112c0) at thread/qthread_unix.cpp:297
#4  0xb71d2c5b in QThread::msleep (msecs=<value optimized out>) at thread/qthread_unix.cpp:323
#5  0xb7f68bfd in net::DownloadThread::update () from /usr/lib/libbtcore.so.12
#6  0xb7f69498 in net::NetworkThread::run () from /usr/lib/libbtcore.so.12
#7  0xb71d3132 in QThreadPrivate::start (arg=0xa0fa330) at thread/qthread_unix.cpp:188
#8  0xb5d0c4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#9  0xb661249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xa4e10b90 (LWP 8021)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb5d100e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb66212ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb71d4172 in QWaitCondition::wait (this=0xa0fa618, mutex=0xa0fa61c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb7f6814e in net::UploadThread::update () from /usr/lib/libbtcore.so.12
#5  0xb7f69498 in net::NetworkThread::run () from /usr/lib/libbtcore.so.12
#6  0xb71d3132 in QThreadPrivate::start (arg=0xa0fa5e0) at thread/qthread_unix.cpp:188
#7  0xb5d0c4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb661249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xa460fb90 (LWP 8022)):
#0  0xb8061430 in __kernel_vsyscall ()
#1  0xb5d100e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb66212ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb71d4172 in QWaitCondition::wait (this=0xb3718bf4, mutex=0xb3718bf0, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb7f6c9d2 in net::ReverseResolverThread::run () from /usr/lib/libbtcore.so.12
#5  0xb71d3132 in QThreadPrivate::start (arg=0xb3718be8) at thread/qthread_unix.cpp:188
#6  0xb5d0c4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb661249e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb580b700 (LWP 7608)):
[KCrash Handler]
#6  0xb8061430 in __kernel_vsyscall ()
#7  0xb65596d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb655b098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb67aa8f8 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6
#10 0xb67a87d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67a8812 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67a88cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb72dd578 in QMetaObject::activate (sender=0xa1a7b64, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3123
#14 0xb72dde42 in QMetaObject::activate (sender=0xa1a7b64, m=0xb73ba904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#15 0xb7319687 in QTimer::timeout (this=0xa1a7b64) at .moc/release-shared/moc_qtimer.cpp:128
#16 0xb72e35ce in QTimer::timerEvent (this=0xa1a7b64, e=0xbff7dafc) at kernel/qtimer.cpp:261
#17 0xb72d816f in QObject::event (this=0xa1a7b64, e=0xbff7dafc) at kernel/qobject.cpp:1075
#18 0xb68ffd3c in QApplicationPrivate::notify_helper (this=0xa11b708, receiver=0xa1a7b64, e=0xbff7dafc) at kernel/qapplication.cpp:4056
#19 0xb690803e in QApplication::notify (this=0xbff7dd8c, receiver=0xa1a7b64, e=0xbff7dafc) at kernel/qapplication.cpp:3603
#20 0xb79f049d in KApplication::notify (this=0xbff7dd8c, receiver=0xa1a7b64, event=0xbff7dafc) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#21 0xb72c7bcb in QCoreApplication::notifyInternal (this=0xbff7dd8c, receiver=0xa1a7b64, event=0xbff7dafc) at kernel/qcoreapplication.cpp:610
#22 0xb72f6d51 in QTimerInfoList::activateTimers (this=0xa124e6c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 0xb72f33a0 in timerSourceDispatch (source=0xa124e38) at kernel/qeventdispatcher_glib.cpp:165
#24 0xb5c4bb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb5c4f0eb in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb5c4f268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb72f32f8 in QEventDispatcherGlib::processEvents (this=0xa0f7fa8, flags={i = -1074275208}) at kernel/qeventdispatcher_glib.cpp:327
#28 0xb69a1a75 in QGuiEventDispatcherGlib::processEvents (this=0xa0f7fa8, flags={i = -1074275160}) at kernel/qguieventdispatcher_glib.cpp:202
#29 0xb72c61fa in QEventLoop::processEvents (this=0xbff7dd20, flags={i = -1074275096}) at kernel/qeventloop.cpp:149
#30 0xb72c6642 in QEventLoop::exec (this=0xbff7dd20, flags={i = -1074275032}) at kernel/qeventloop.cpp:201
#31 0xb72c8ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0xb68ffbb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0x080678d1 in main ()

Reported using DrKonqi
Comment 1 Joris Guisson 2009-11-22 10:53:16 UTC

*** This bug has been marked as a duplicate of bug 214103 ***