Bug 183908 - kopete crashes randomly (it seems)
Summary: kopete crashes randomly (it seems)
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Other
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-02-10 13:42 UTC by Richard Homonnai
Modified: 2018-10-21 04:51 UTC (History)
1 user (show)

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 Richard Homonnai 2009-02-10 13:42:32 UTC
Version:            (using KDE 4.2.0)
OS:                OS X
Installed from:    Unspecified Other

Using KDE 4.2.0 from MacPorts with Apple's GCC 4.2.

The following crash occurs from time to time, and it starts getting annoying ;)

Application: Kopete (kopete), signal SIGSEGV
Attaching to process 95970.
Reading symbols for shared libraries . done
Reading symbols for shared libraries .................................................................................................................................................................................................................. done
[Current thread is 1 (process 95970 thread 0x20b)]

Thread 3 (process 95970 thread 0x1bbe7):
#0  0x92f2020e in semaphore_wait_signal_trap ()
#1  0x92f52206 in _pthread_cond_wait ()
#2  0x92f97539 in pthread_cond_wait ()
#3  0x01524106 in QWaitCondition::wait ()
#4  0x00ce1d54 in QHostInfoAgent::run ()
#5  0x01522d0b in QThreadPrivate::start ()
#6  0x92f51095 in _pthread_start ()
#7  0x92f50f52 in thread_start ()

Thread 2 (process 95970 thread 0x4403):
#0  0x92f6f6f2 in select$DARWIN_EXTSN ()
#1  0x941f751f in __CFSocketManager ()
#2  0x92f51095 in _pthread_start ()
#3  0x92f50f52 in thread_start ()

Thread 1 (process 95970 thread 0x20b):
[KCrash Handler]
#5  0x01623726 in QObject::connect ()
#6  0x00396063 in Kopete::MessageHandler::handleMessageInternal ()
#7  0x00394ae2 in Kopete::ProcessMessageTask::start ()
#8  0x00394a85 in Kopete::ProcessMessageTask::qt_metacall ()
#9  0x01620280 in QMetaObject::activate ()
#10 0x01629be2 in QSingleShotTimer::timeout ()
#11 0x01629c7c in QSingleShotTimer::timerEvent ()
#12 0x01620c38 in QObject::event ()
#13 0x017da47f in QApplicationPrivate::notify_helper ()
#14 0x017dc16c in QApplication::notify ()
#15 0x00efb7f3 in KApplication::notify ()
#16 0x0160eb61 in QCoreApplication::notifyInternal ()
#17 0x0183b5cc in QEventDispatcherMacPrivate::activateTimers ()
#18 0x0183c133 in QEventDispatcherMac::processEvents ()
#19 0x0160e121 in QEventLoop::processEvents ()
#20 0x0160e1ed in QEventLoop::exec ()
#21 0x01612191 in QCoreApplication::exec ()
#22 0x00039ee5 in main ()
Comment 1 Dario Andres 2009-02-10 14:04:46 UTC
Not sure if MacPorts provide them but you will need debug symbols for Kopete
Thanks
Comment 2 Richard Homonnai 2009-02-10 15:36:05 UTC
(In reply to comment #1)
> Not sure if MacPorts provide them but you will need debug symbols for Kopete
> Thanks
> 

How do I check that? I have plenty of Linux experience, and I am not even afraid of gdb ;)
Comment 3 Dario Andres 2009-02-10 15:41:50 UTC
Not really sure about the MacPorts systems but it should be packages with the "-debug" , "-dbg" , or "-debuginfo" postfix 
Also, look at: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks
Comment 4 Dario Andres 2009-03-14 23:02:31 UTC
No response from reporter. Closing as REMIND.
Comment 5 Dario Andres 2009-03-15 12:29:12 UTC
Marking as NEEDSINFO
Comment 6 Richard Homonnai 2009-03-15 22:43:16 UTC
Sorry, I wasn't able to set MacPorts that way.
And the problem only occurs on Mac it seems.
Comment 7 Andrew Crouthamel 2018-09-19 04:38:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-21 04:51:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!