Created attachment 56672 [details]
core

I'm also using licq and unfortunately it isn't the most stable piece of software, I also have crashes from time to time. I imagine this would be hard to locate and have several reasons.

KDE-Maintainers: Can you help here? If not, please assign it back to the screening-team.

I have backtrace. I'm not sure if the problem is in QTlibs. If not, reassign this bug to me. 

(gdb) bt
#0  0x409347f6 in QListViewItem::takeItem ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#1  0x40945731 in QListViewItem::~QListViewItem ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#2  0x405433f3 in ~CUserViewItem (this=0x8243f28) at userbox.cpp:252
#3  0x404f2f4c in CMainWindow::slot_updatedUser (this=0x8229f58, sig=0x826f6e8)
    at mainwin.cpp:1595
#4  0x404f9085 in CMainWindow::qt_invoke (this=0x8229f58, _id=53, 
    _o=0x4185ee94) at mainwin.moc:504
#5  0x40856b99 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0x4052747f in CSignalManager::signal_updatedUser (this=0x820ef60, 
    t0=0x826f6e8) at sigman.moc:201
#7  0x4052847c in CSignalManager::ProcessSignal (this=0x820ef60, s=0x826f6e8)
    at sigman.cpp:88
#8  0x4052864e in CSignalManager::slot_incoming (this=0x820ef60)
    at sigman.cpp:52
#9  0x40528692 in CSignalManager::qt_invoke (this=0x820ef60, _id=2, 
    _o=0x4185efe4) at sigman.moc:411
#10 0x40856b99 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40857262 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#12 0x40b8be30 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40874960 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x407f8117 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x407f8db1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x407ecee1 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x407a763e in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x4080ec61 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x4080eade in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x407f7bbf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x404d95c0 in CLicqGui::Run (this=0x8187a60, _licqDaemon=0x8186d90)
    at licqgui.cpp:411
#22 0x404daa3b in LP_Main (_licqDaemon=0x8186d90) at licqgui.cpp:174
#23 0x404daa8d in LP_Main_tep (p=0x8186d90) at licq_plugin.h:119
#24 0x40199297 in start_thread () from /lib/libpthread.so.0
#25 0x403aba8e in clone () from /lib/libc.so.6
#26 0x4185fbb0 in ?? ()

its not necessarily Qt libs, actually quite unlikely. more looks like the plugin got a message for a nick list entry update and it crashes while performing the update. it could be anything, from a memory corruption to an error in the licq state handling. 

is it reproducible? do you know when it happens? I was a licq hacker back in the dark times.. ;)

It's random, but in this time more likely. It crashes always right after login to the ICQ server. More likely it is my problem, not QT's problem. So you can reassign this bug to me. I'm just trying ElectricFence, but without any clue to the problem.

you can reassign on your own ;)

better use valgrind btw 

I've got it. If a pending message arrives, licq crashes. 
 Sorry for disturbing.

It lookes like it is a problem of qt 3.3.5.
Please see this url
http://lists.trolltech.com/qt-interest/2005-11/thread00128-0.html
 What is your opinion?

we've aleady added the fix for this to our qt3 package. 

-------------------------------------------------------------------
Fri Nov 11 15:48:07 CET 2005 - dmueller@suse.de

- avoid crashes after QListView::clear()

You could told me. Therefore I was asking if it is a QT bug or not. I spend hours debuging licq in vain. 

I'm going to test if it still crashes.

sorry :)

for my defense, you asked me before I was aware of the bug :)

With patched qt3, licq doesn't crash anymore.