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

List:       kde-devel
Subject:    Re: Strange kmail segfault in 1.1
From:       Sven Radej <sven () lisa ! exp ! univie ! ac ! at>
Date:       1999-06-16 15:08:51
[Download RAW message or body]

On Wed, 16 Jun 1999, Waldo Bastian wrote:
(...)
>A way to trace down this error is to find the point where the QAccel object
>is still ok, and then set breakpoints at regular intervals in your path of
>execution. At each breakpoint you check whether the QAccel object still
>makes sense. If there are points where the pointer to the QAccel object
>might be changed you should add breakpoints there as well, since otherwise
>you might be looking at a QAccel which isn't used any more.
>
>This way you will be able to narrow down on the place where the corruption
>takes place. And yes, it is a boring job :)
>
>(For things like this you need a logic analyzer attached to your CPU :)

Don accused QLabel::setBuddy and he was right. I don't know was it intuition,
logic analyzer, experience, sorcery, witchcraft, but he was right.
Fix is in CVS (That was all about kmail in 1.1 branch.)

I'd like to thank everybody (esp. Don!) for helping to resolve this... this...
this.

-- 
Sven Radej      radej@kde.org
KDE developer   Visit http://www.kde.org

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