Summary: | KSCD crashes with signal 11 on return from freedb.org lookup on new disc | ||
---|---|---|---|
Product: | kscd | Reporter: | Brandon Gingras <brandongingras> |
Component: | general | Assignee: | Aaron J. Seigo <aseigo> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | gshugars, kaplun, leon, marc, markd, n2uro, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Brandon Gingras
2003-03-15 02:27:24 UTC
Also occurs: KDE 3.1.1, Redhat 8.0 Packages (from ftp.kde.org), when using the kscdrc configuration file I copied from my home computer (otherwise, kscd at work acts completely strange for me). My home computer does not seem to have this issue, although I will double check that. Note that Bug #56344 (which I filed) should NOT be closed unless someone wants a new one. KSCD under the Redhat 8.0 packages is acting completely wierd and erractic, but I will not update said bug for several hours until I get back from work and try my RedHat 8.0 KDE package generated kscdrc on my home computer (to see if it causes problems there as well). (no debugging symbols found)...0x40eed587 in waitpid () from /lib/libpthread.so.0 #0 0x40eed587 in waitpid () from /lib/libpthread.so.0 #1 0x4060c1a9 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 #2 0x40eec1cd in __pthread_clock_settime () from /lib/libpthread.so.0 #3 0x4103b568 in killpg () from /lib/libc.so.6 #4 0x40c9cef3 in QSocket::qt_invoke(int, QUObject*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #5 0x4098d599 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #6 0x4098d675 in QObject::activate_signal(int, int) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #7 0x40c70592 in QSocketNotifier::activated(int) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #8 0x409a9ca0 in QSocketNotifier::event(QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #9 0x4092f594 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #10 0x4092ed65 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #11 0x4059e4b9 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #12 0x4090a888 in QEventLoop::activateSocketNotifiers() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #13 0x408e7fd3 in QEventLoop::processEvents(unsigned) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #14 0x40943266 in QEventLoop::enterLoop() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #15 0x40943108 in QEventLoop::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #16 0x4092f7c1 in QApplication::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #17 0x08067257 in main () #18 0x41028907 in __libc_start_main () from /lib/libc.so.6 Subject: Re: KSCD crashes with signal 11 on return from freedb.org lookup on new disc On Thursday 27 March 2003 12:08, you wrote: > ------- Additional Comments From n2uro@aol.com 2003-03-27 20:08 ------- > Also occurs: KDE 3.1.1, Redhat 8.0 Packages (from ftp.kde.org), when using > the kscdrc configuration file I copied from my home computer (otherwise, > kscd at work acts completely strange for me). My home computer does not > seem to have this issue, although I will double check that. hrm... i don't seem to have this problem here, though i'm still using Qt 3.1.1 here, so that might be it.. i plan on visiting these bug reports as soon as i upgrade to 3.1.2 > Note that Bug #56344 (which I filed) should NOT be closed unless someone > wants a new one. no one's going to close it until the problem is determined and fixed or sent elsewhere... I have the same problem using precompiled packages for SuSE 7.3, KDE 3.1.1, QT 3.1.1. the player always chrashes after a freedb.org query and after restart he uses the data from the local disk *** Bug 56881 has been marked as a duplicate of this bug. *** *** Bug 56344 has been marked as a duplicate of this bug. *** Could this be related to a QT bug the Gentoo distribution was told about, making this a QT issue or a kscd's usage of QT issue? http://bugs.gentoo.org/show_bug.cgi?id=19005 (kscd crashing on CDDB lookups is mentioned in this bug several times.) *** Bug 57368 has been marked as a duplicate of this bug. *** If you comment out the delete sock; in the following function the error does not occur. Otherwise I have two different machines with this bug. 1. RedHat 9 with selfcompiled KDE 3.1.1a and QT 3.1.2 2. Suse Linux 8.2 with selfcompiled KDE 3.1.1a and QT 3.1.2 cddb.cpp: around Line 420 void CDDB::cddb_close() { timeouttimer.stop(); kdDebug() << "SOCKET CONNECTION TERMINATED\n" << endl; connected = false; if(sock) { sock->close(); disconnect(sock, SIGNAL(connected()), this, SLOT(slotConnected())); disconnect(sock, SIGNAL(connectionClosed()), this, SLOT(slotConnectionClosed())); disconnect(sock, SIGNAL(error(int)), this, SLOT(slotErrorConnection(int))); disconnect(sock,SIGNAL(readyRead()),this,SLOT(cddb_read())); delete sock; sock = 0L; } } According to the QSocket documentation this code seems valid but the error occurs. I have not looked much at this bug, because I can live with this memory leak, but maybe this class is used in another thread than the main thread? This would explain the error. *** Bug 58412 has been marked as a duplicate of this bug. *** This happens to me too -> eject CD, insert new CD, click freedb button, click "fetch info", KSCD segfaults. Upon restart, the properly fetched freedb info is right there. Qt: 3.1.2 KDE: 3.1.1 kscd: 1.3.3 kscd now uses a new cddb library in place of its own cddb support. I have exactly the same problem on Mandrake 9.2 with gcc version 3.3.1, this is what the backtrace gave.. (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40f83656 in waitpid () from /lib/i686/libpthread.so.0 #0 0x40f83656 in waitpid () from /lib/i686/libpthread.so.0 #1 0x40661fda in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 Also occurs on Fedora Core 1 (Yarrow), kernel 2.4.22-1.2149.nptl; KDE 3.1.4-4Redhat; KsCD 1.3.3; Qt 1:3.1.2-14. Backtrace: (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1085290560 (LWP 4194)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x00b58c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #0 0x00b58c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x00177b03 in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #2 0x0711b6fc in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 |