Version: (using KDE KDE 3.0.3) Installed from: Mandrake RPMs Compiler: gcc 3.2 OS: Linux I've reported a crash of the appliction closing noatun after I loaded a playlist file. This is the backtrace (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x41909739 in wait4 () from /lib/i686/libc.so.6 #0 0x41909739 in wait4 () from /lib/i686/libc.so.6 #1 0x41986340 in sys_sigabbrev () from /lib/i686/libc.so.6 #2 0x415f9a73 in waitpid () from /lib/i686/libpthread.so.0 #3 0x40b10f55 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 and the console output mcop warning: user defined signal handler found for SIG_PIPE, overriding Internal Vis Started 0 KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = noatun path = <unknown> pid = 2242 KDirWatch: /etc/security/fileshare.conf is a file. Use addFile! Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) Mutex destroy failure: Device or resource busy
The mp3s were in a cd but there were no troubles mounting the device, in fact after the crash I re-tried launching noatun and the application worled properly
The interesting part is missing from the backtrace - this is only the traceback for the tool that reports the crash... (isn't this a bug in that tool?) The same might be true for the second case - were there any output before "Internal Vis"
I just saved a copy of the backtrace from the KDE crash reporter, actually I don't know if there is a bug in that tool, anyway the tool gives this information: (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)... (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)...0x41909739 in wait4 () from /lib/i686/libc.so.6 #0 0x41909739 in wait4 () from /lib/i686/libc.so.6 #1 0x41986340 in sys_sigabbrev () from /lib/i686/libc.so.6 #2 0x415f9a73 in waitpid () from /lib/i686/libpthread.so.0 #3 0x40b10f55 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 nothing else. I don't know if it is supposed to give other information. I give you the console output too: [taipan@localhost taipan]$ noatun & [1] 2512 [taipan@localhost taipan]$ mcop warning: user defined signal handler found for SIG_PIPE, overriding Internal Vis Starded 0 [taipan@localhost taipan]$ KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = noatun path = <unknown> pid = 2513 KDirWatch: /etc/security/fileshare.conf is a file. Use addFile! > ------- Additional Comments From roger.larsson@norran.net 2002-11-06 19:25 > ------- The interesting part is missing from the backtrace - this is only > the traceback for the tool that reports the crash... (isn't this a bug in > that tool?) > > The same might be true for the second case - were there any output before > "Internal Vis"
Subject: Re: crash closing the application I just saved a copy of the backtrace from the KDE crash reporter, actually I don't know if there is a bug in that tool, anyway the tool gives this information: (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)... (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)...0x41909739 in wait4 () from /lib/i686/libc.so.6 #0 0x41909739 in wait4 () from /lib/i686/libc.so.6 #1 0x41986340 in sys_sigabbrev () from /lib/i686/libc.so.6 #2 0x415f9a73 in waitpid () from /lib/i686/libpthread.so.0 #3 0x40b10f55 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 nothing else. I don't know if it is supposed to give other information. I give you the console output too: [taipan@localhost taipan]$ noatun & [1] 2512 [taipan@localhost taipan]$ mcop warning: user defined signal handler found for SIG_PIPE, overriding Internal Vis Starded 0 [taipan@localhost taipan]$ KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = noatun path = <unknown> pid = 2513 KDirWatch: /etc/security/fileshare.conf is a file. Use addFile! > ------- Additional Comments From roger.larsson@norran.net 2002-11-06 19:25 > ------- The interesting part is missing from the backtrace - this is only > the traceback for the tool that reports the crash... (isn't this a bug in > that tool?) > > The same might be true for the second case - were there any output before > "Internal Vis"
dunno what this is, havn't seen it since.