You are not logged in.

1

Wednesday, March 21st 2007, 12:10pm

crash handler?

Hi,

I'm a total newbie (100%), i downloaded a few how-to's and books from the repo's on PCLinuxOS (as that is the distro i have), when it finished i had a crash report, i've been to the "bugs.kde" but because i'm not sure of the way it works i got lost through not understanding the report, somehow when i registered i got directed here,so here's what i have:

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)

>snipped about 50 lines<

(no debugging symbols found)
[KCrash handler]
#6 0x432fa846 in operator== () from /usr/lib/qt3/lib/libqt-mt.so.3
#7 0x43cc2f4a in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#8 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#9 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#10 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#11 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#12 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#13 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#14 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#15 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#16 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#17 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#18 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#19 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#20 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#21 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#22 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#23 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#24 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#25 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#26 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#27 0x43cc096a in KDirWatchPrivate::useFAM () from /usr/lib/libkio.so.4
#28 0x43cc2fed in KDirWatchPrivate::checkFAMEvent () from /usr/lib/libkio.so.4
#29 0x43cc2ab5 in KDirWatchPrivate::famEventReceived ()
from /usr/lib/libkio.so.4
#30 0x43cc4359 in KDirWatchPrivate::qt_invoke () from /usr/lib/libkio.so.4
#31 0x430417f7 in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x430418ee in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x43333498 in QSocketNotifier::activated ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x4305bd61 in QSocketNotifier::event ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x42fe807f in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x42fe7617 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0x435d1f2b in KApplication::notify () from /usr/lib/libkdecore.so.4
#38 0x42fd7e2e in QEventLoop::activateSocketNotifiers ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x42f92d57 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0x42ff87ca in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x42ff86b4 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0x42fe8290 in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0xb7f80103 in kdemain () from /usr/lib/libkdeinit_kded.so
#44 0xb7f88910 in kdeinitmain () from /usr/lib/kde3/kded.so
#45 0x0804d65d in ?? ()
#46 0x00000002 in ?? ()
#47 0x080828a8 in ?? ()
#48 0x428f5b84 in ?? () from /lib/i686/libpthread.so.0
#49 0x428f5b84 in ?? () from /lib/i686/libpthread.so.0
#50 0x00000000 in ?? ()

Any help as to what bug/s i'm looking for is appreciated.

T.I.A

bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

2

Sunday, March 25th 2007, 3:10pm

RE: crash handler?

Crash reports should be registered at bugs.kde.org , where did you exactly relocated to this forum?

And never forget to include a description how the crash happened, only a bare backtrace doesn't help developers to solve the problem.
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

3

Sunday, March 25th 2007, 10:44pm

RE: crash handler?

Quoted

Originally posted by bram85
Crash reports should be registered at bugs.kde.org , where did you exactly relocated to this forum?

And never forget to include a description how the crash happened, only a bare backtrace doesn't help developers to solve the problem.


I did go to the bugs site but what happened from there i don't know, somehow i ended up on here, not once but twice, so i just left it.

Apologies for my mistake.