Subject: Re: [Kopete-devel]  New: crashes logon / logoff

On Tuesday 18 February 2003 22:31, Frederik Vos wrote:
> Kopete 0.6.1, Suse 8.1 with official suse builds 3.1 (but the same for the
> not official kde builds 3.1) crashes several times. Most of the time if i
> log off/log on. Always the same backtrace.

Did you compile Kopete yourself or did you use rpms? Also, did you use the 
correct set of KDE header files if you're mixing KDE versions?

If you're trying to run a prebuilt kopete against the wrong KDE version you 
might be hitting binary compatibility problems. At least the backtrace seems 
to indicate something in that direction.

Subject: Re:  crashes logon / logoff

On Tuesday 18 February 2003 22:35, Martijn Klingens wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=54827
>
>
>
>
> ------- Additional Comments From klingens@kde.org  2003-02-18 22:35 -------
> Subject: Re: [Kopete-devel]  New: crashes logon / logoff
>
> On Tuesday 18 February 2003 22:31, Frederik Vos wrote:
> > Kopete 0.6.1, Suse 8.1 with official suse builds 3.1 (but the same for
> > the not official kde builds 3.1) crashes several times. Most of the time
> > if i log off/log on. Always the same backtrace.
>
> Did you compile Kopete yourself or did you use rpms? Also, did you use the
> correct set of KDE header files if you're mixing KDE versions?

it's a clean install of Suse (minimal graphical without KDE) and after that 
install, only the new official 3.1 builds from Suse are installed.
I have compiled Kopete myself with only the parameter --prefix=/opt/kde3

Subject: Re: [Kopete-devel]  crashes logon / logoff

On Wednesday 19 February 2003 08:30, Frederik Vos wrote:
> I have compiled Kopete myself with only the parameter --prefix=/opt/kde3

Hmm, that cannot be it then.

Could you please rebuild Kopete with '--enable-debug=full' added to the 
configure line? That way we get some more extensive backtrace, which might be 
more useful.

Also, trying to run Kopete from valgrind might be an idea to see where exactly 
it goes wrong.

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 10:29, Martijn Klingens wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=54827
>
>
>
>
> ------- Additional Comments From klingens@kde.org  2003-02-19 10:29 -------
> Subject: Re: [Kopete-devel]  crashes logon / logoff
>
> On Wednesday 19 February 2003 08:30, Frederik Vos wrote:
> > I have compiled Kopete myself with only the parameter --prefix=/opt/kde3
>
> Hmm, that cannot be it then.
>
> Could you please rebuild Kopete with '--enable-debug=full' added to the
> configure line? That way we get some more extensive backtrace, which might
> be more useful.

i did, no crashes any longer :) (very strange)
so compiled it back, and there are the crashes again ... going to install 
valgrind

Subject: Re: [Kopete-devel]  crashes logon / logoff

On Wednesday 19 February 2003 12:10, Frederik Vos wrote:
> i did, no crashes any longer :) (very strange)
> so compiled it back, and there are the crashes again ... going to install 
> valgrind

You only have problems with a release build? Hmm, that's not good.

Release builds have no symbols, making debugging very hard or even impossible.

I _hope_ that valgrind can shed a light on this, but I no longer hold my 
breath :( It might be timing related, which could explain the crashes only in 
a release build.

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 14:13, Martijn Klingens wrote:

> I _hope_ that valgrind can shed a light on this, but I no longer hold my
> breath :( It might be timing related, which could explain the crashes only
> in a release build.

valgrind:

kopete: [JabberContact] Updating contact 49048900@icq.jabber.or.id  to 
STATUS_AW
AY (Reason: away)
kopete: [JabberMessageManager] slotMessageSent called: moeizaam gedoe
==26947==
==26947== Invalid read of size 4
==26947==    at 0x4156A9EE: __dynamic_cast (in /usr/lib/libstdc++.so.5.0.0)
==26947==    by 0x47B2B8B9: JabberMessageManager::km2jm(KopeteMessage const&, 
Ja            bber::Message&) (in /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    by 0x47B2BDE9: 
JabberMessageManager::slotMessageSent(KopeteMessage             const&, 
KopeteMessageManager*) (in /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    by 0x47B2B391: JabberMessageManager::qt_invoke(int, QUObject*) 
(in             /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    Address 0x44FFBD48 is not stack'd, malloc'd or free'd
==26947==
==26947== Invalid read of size 4
==26947==    at 0x4156A9F2: __dynamic_cast (in /usr/lib/libstdc++.so.5.0.0)
==26947==    by 0x47B2B8B9: JabberMessageManager::km2jm(KopeteMessage const&, 
Ja            bber::Message&) (in /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    by 0x47B2BDE9: 
JabberMessageManager::slotMessageSent(KopeteMessage             const&, 
KopeteMessageManager*) (in /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    by 0x47B2B391: JabberMessageManager::qt_invoke(int, QUObject*) 
(in             /opt/kde3/lib/kde3/kopete_jabber.so)
==26947==    Address 0x6F0027 is not stack'd, malloc'd or free'd
==26947== Warning: client attempted to close Valgrind's logfile fd (2).
==26947==    Use --logfile-fd=<number> to select an alternative logfile fd.
KCrash: Application 'kopete' crashing...

backtrace


0x40181d5a in vgPlain_do_syscall () from /usr/lib/valgrind/valgrind.so
#0  0x40181d5a in vgPlain_do_syscall () from /usr/lib/valgrind/valgrind.so
#1  0x416d5c90 in __DTOR_END__ () from /lib/libc.so.6
#2  0x414c458d in waitpid () from /usr/lib/valgrind/libpthread.so.0
#3  0x40bddb0d in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x4016f0dc in vgPlain_signalreturn_bogusRA ()
   from /usr/lib/valgrind/valgrind.so
#5  0x47b2b8ba in JabberMessageManager::km2jm(KopeteMessage const&, 
Jabber::Message&) () from /opt/kde3/lib/kde3/kopete_jabber.so
#6  0x47b2bdea in JabberMessageManager::slotMessageSent(KopeteMessage const&, 
KopeteMessageManager*) () from /opt/kde3/lib/kde3/kopete_jabber.so
#7  0x47b2b392 in JabberMessageManager::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/kde3/kopete_jabber.so
#8  0x40f4c309 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x4025a2a1 in KopeteMessageManager::messageSent(KopeteMessage const&, 
KopeteMessageManager*) () from /opt/kde3/lib/libkopete.so.1
#10 0x40256bdc in KopeteMessageManager::slotMessageSent(KopeteMessage const&)
    () from /opt/kde3/lib/libkopete.so.1
#11 0x4025a88d in KopeteMessageManager::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/libkopete.so.1
#12 0x47b2b368 in JabberMessageManager::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/kde3/kopete_jabber.so
#13 0x40f4c309 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x4029d1f7 in Kopete::ChatView::SendMessage(KopeteMessage const&) ()
   from /opt/kde3/lib/libkopete.so.1
#15 0x4029a1b4 in Kopete::ChatView::sendMessage() ()
   from /opt/kde3/lib/libkopete.so.1
#16 0x4029a577 in Kopete::ChatView::eventFilter(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkopete.so.1
#17 0x40f4a07e in QObject::activate_filters(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40f49fa1 in QObject::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40f8053c in QWidget::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x410853bd in QTextEdit::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40eee2e4 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40eedc5c in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40b6ffc9 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#24 0x40e93b8c in QETWidget::translateKeyEvent(_XEvent const*, bool) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40e8fa90 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40ea4eda in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40f01fa6 in QEventLoop::enterLoop() ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40f01e48 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40eee511 in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x0805e073 in main ()
#31 0x415d54a2 in __libc_start_main () from /lib/libc.so.6

Subject: Re: [Kopete-devel]  crashes logon / logoff

I hope some Jabber developer knows what this means :)

Anyway, this is the normal version, right?

Does the --enable-debug=full version tell us some more, like line number debug 
info?

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 15:28, Martijn Klingens wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=54827
>
>
>
>
> ------- Additional Comments From klingens@kde.org  2003-02-19 15:28 -------
> Subject: Re: [Kopete-devel]  crashes logon / logoff
>
> I hope some Jabber developer knows what this means :)
>
> Anyway, this is the normal version, right?

yes, building the normal way, otherwise: with --enable-debug=full it doesn't 
crash ...

Subject: Re: [Kopete-devel]  crashes logon / logoff

On Wednesday 19 February 2003 15:37, Frederik Vos wrote:
> yes, building the normal way, otherwise: with --enable-debug=full it doesn't 
> crash ...

Valgrind *may* still be able to spot inconsistencies though.

I don't have high hopes here, but line number info would definitely help...

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 14:13, Martijn Klingens wrote:

going to test further with 0.6.1a (crashes also)
i'm also curious or more people have this problem .. maybe it's me doing 
something wrong

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 14:13, you wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=54827

The good news for 0.6.1a is that it only crashes one time now (instead of 3 
times)
in older version it could crash if you start or end the program and by 
changing the status from offline to online.
Now only with the status from offline to online. In both cases only if you 
compile it without full-debug.
I'm not a programmer, but what means: 
Address .... is not stack'd, malloc'd or free'd

Subject: Re: [Kopete-devel]  crashes logon / logoff

On Thursday 20 February 2003 14:06, Frederik Vos wrote:
> I'm not a programmer, but what means: 
> Address .... is not stack'd, malloc'd or free'd

Some part of code is using a pointer pointing into nowhere in particular. 
Probably a dangling pointer to an object that's already freed.

You don't get the same valgrind error (with or without actually crashing) in a 
debug build?

I'm intrigued to know why...

Subject: Re:  crashes logon / logoff

On Thursday 20 February 2003 14:23, you wrote:

> You don't get the same valgrind error (with or without actually crashing)
> in a debug build?

no, the error is not there

> I'm intrigued to know why...

me too :)

Subject: Re:  crashes logon / logoff

On Wednesday 19 February 2003 16:04, Martijn Klingens wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=54827

did several tests this weekend,
two things for sure now: it's related to the jabber implementation, other 
plugins doesn't have this probleme.
tried it on another computer with exactly the same installation as my computer 
(autoyast install, so we can be sure about that), and on that computer there 
is no single problem with Kopete ...

*** This bug has been marked as a duplicate of 54515 ***

Hi, 
 
i have the same problem but only the icq plugin enabled. If i try after a short 
connection time to dis- and reconnect icq, mostly, but not in general, kopete 0.6.1a 
crashes with the following stack-trace: 
 
[New Thread 1024 (LWP 3700)] 
[New Thread 2049 (LWP 3701)] 
0x4127a099 in wait4 () from /lib/libc.so.6 
#0  0x4127a099 in wait4 () from /lib/libc.so.6 
#1  0x412f4bd8 in __DTOR_END__ () from /lib/libc.so.6 
#2  0x41152072 in waitpid () from /lib/libpthread.so.0 
#3  0x4090983e in KCrash::defaultCrashHandler () 
   from /opt/kde3/lib/libkdecore.so.4 
#4  0x4114fa74 in pthread_sighandler () from /lib/libpthread.so.0 
#5  <signal handler called> 
#6  0x40dc0017 in QSocket::sn_read () from /usr/lib/libqt-mt.so.3 
#7  0x40ec95b9 in QSocket::qt_invoke () from /usr/lib/libqt-mt.so.3 
#8  0x40c433c4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 
#9  0x40c4354b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 
#10 0x40e9f23d in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3 
#11 0x40c5a22f in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3 
#12 0x40bf809a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 
#13 0x40bf7ea7 in QApplication::notify () from /usr/lib/libqt-mt.so.3 
#14 0x408a7d5b in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 
#15 0x40bdbfd7 in QEventLoop::activateSocketNotifiers () 
   from /usr/lib/libqt-mt.so.3 
#16 0x40bbe4cb in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 
#17 0x40c08520 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 
#18 0x40c08467 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 
#19 0x40bf8216 in QApplication::exec () from /usr/lib/libqt-mt.so.3 
#20 0x0805d862 in main () 
#21 0x411ef9ed in __libc_start_main () from /lib/libc.so.6 
 
kopete is selfcompiled with --disable-debug. kde 3.1.1. is installed from suse 8.0 
packages. 
 
 

This has nothing to do with icq and the crash you experienced is fixed, just wait for Kopete 0.6.2 
which is meant to be released soon.