[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [Kopete-devel] [Bug 52406] when removing a (protocol) plug in kopete crashes
From:       Martijn Klingens <klingens () kde ! org>
Date:       2002-12-30 22:23:48
[Download RAW message or body]

On Monday 30 December 2002 22:08, Pupeno wrote:
> > While running with valgrind, as usual, it didn't crash :(

No crash doesn't mean no problem though :)

Especially using uninitialized memory tends to not crash under valgrind 
because valgrind afaik resets memory to all zeroes, something malloc does 
not. You do get a crystal-clear warning about that however, so it might still 
be interesting to have.

Anyway, this backtrace is rather interesting too:

> ==2447== Use of uninitialised value of size 4
> ==2447==    at 0x410D18DD: QObject::checkConnectArgs(char const*, QObject
> const*, char const*) (kernel/qobject.cpp:1513)

this is only possible if checkConnectArgs is called with an invalid value for 
member, i.e. 'connect( "mySignal", myObject, mySlot )', mySlot being a char* 
pointing into illegal memory. Only possible if something is going seriously 
wrong.

> ==2447==    by 0x4120883E: QWidgetStack::minimumSizeHint() const (in
> /home/pupeno/src/kde/kde-head/qt-copy/lib/libqt-mt.so.3.1.1)

But WTF does the minimum size hint of a QWidgetStack have to do with 
checkConnectArgs? Those really don't belong together. Also, QObject above has 
full debug info, QWidgetStack has not. Any idea why? Are you mixing two Qt 
versions?

Looks like the protocols are deleted twice somehow. I have no idea why though. 
:(
-- 
Martijn

_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]