Bug 55976 - KSCD crashes with signal 11 on return from freedb.org lookup on new disc
Summary: KSCD crashes with signal 11 on return from freedb.org lookup on new disc
Status: RESOLVED NOT A BUG
Alias: None
Product: kscd
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
: 56344 56881 57368 58412 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-15 02:27 UTC by Brandon Gingras
Modified: 2004-01-28 02:51 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brandon Gingras 2003-03-15 02:27:24 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc version 2.95.3 20010315 (release) 
OS:          Linux

After KSCD performs a remote cddb lookup on a previously unknown cd on freedb.org (not local lookup) the program crashes as soon as the lookup is finished. It started doing this with the new QT 3.1.2. I went back to my old 3.1.1 libraries and KSCD did not produce a crash. It only crashes after the remote cddb lookup.  When KSCD is restarted after the crash the CDDB information is found on the local list and the disc can then be played.

Here is a bugtrace:
[New Thread 1024 (LWP 6388)]
0x41258b79 in __wait4 () at __wait4:-1
	in __wait4
#0  0x41258b79 in __wait4 () at __wait4:-1
#1  0x412cf988 in __DTOR_END__ () from /lib/libc.so.6
#2  0x41141d9b in waitpid (pid=6389, stat_loc=0x0, options=0)
    at wrapsyscall.c:173
#3  0x405bdf0a in KCrash::defaultCrashHandler ()
   from /opt/kde3.1/lib/libkdecore.so.4
#4  0x4113fc34 in pthread_sighandler (signo=11, ctx=
      {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 3, esi = 135469736, ebp = 3221221516, esp = 3221217372, ebx = 1090668312, edx = 134841272, ecx = 0, eax = 6357024, trapno = 14, err = 4, eip = 1086339370, cs = 35, __csh = 0, eflags = 66183, esp_at_signal = 3221217372, ss = 43, __ssh = 0, fpstate = 0xbfffdde0, oldmask = 2147483648, cr2 = 6357060})
    at signals.c:97
#5  <signal handler called>
#6  0x40c0392a in QSocket::sn_read () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0x40d66cd9 in QSocket::qt_invoke () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x409fd913 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x409fdae3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40d3103b in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40a19d32 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40996c4b in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40996994 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40541b3a in KApplication::notify () from /opt/kde3.1/lib/libkdecore.so.4
#15 0x4096efd3 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x4094e1ba in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x409ad5de in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x409ad53b in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40996e5e in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x08065e3e in main ()
#21 0x411d1b6f in __libc_start_main (main=0x8065b68 <main>, argc=7, 
    ubp_av=0xbffff6b4, init=0x8054920 <_init>, fini=0x80858bc <_fini>, 
    rtld_fini=0x4000af40 <_dl_fini>, stack_end=0xbffff6ac)
    at ../sysdeps/generic/libc-start.c:129
Comment 1 n2uro 2003-03-27 20:08:41 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 
 
Comment 2 Aaron J. Seigo 2003-03-27 20:17:36 UTC
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...

Comment 3 Bastian Ibach 2003-04-03 13:28:03 UTC
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
Comment 4 Aaron J. Seigo 2003-04-10 00:00:04 UTC
*** Bug 56881 has been marked as a duplicate of this bug. ***
Comment 5 Aaron J. Seigo 2003-04-15 18:48:09 UTC
*** Bug 56344 has been marked as a duplicate of this bug. ***
Comment 6 n2uro 2003-04-16 02:55:41 UTC
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.) 
Comment 7 Aaron J. Seigo 2003-04-19 02:12:39 UTC
*** Bug 57368 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Bartoschek 2003-05-08 10:37:27 UTC
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. 
Comment 9 Stephan Kulow 2003-05-13 10:04:20 UTC
*** Bug 58412 has been marked as a duplicate of this bug. ***
Comment 10 sgeier 2003-05-16 07:41:40 UTC
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 
 
Comment 11 Aaron J. Seigo 2003-05-29 00:10:38 UTC
kscd now uses a new cddb library in place of its own cddb support. 
Comment 12 Matt Howe 2003-12-13 03:45:51 UTC
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 
Comment 13 Gordon Shugars 2004-01-28 02:51:27 UTC
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