...and one suggestion
rokrau at yahoo.com
Thu Jun 7 13:23:29 UTC 2001
--- "F at lk Brettschneider" <gigafalk at yahoo.com> wrote:
> That's not the fix of the actual problem.
Yes, i agree, but it still makes sense in my opinion.
> I cannot reproduce this here, it's likely an event timing problem. (I
> should downgrade to a slower computer... ;)
> Please, check if the KWriteDoc already passed the destructor and send
> the backtrace at the destructor breakpoint and the backtrace of the
I can check for whether KWriteDoc has been destructed, can I? How would
I do that? The problem is that the crash is not really reproducable.
I'll send a backtrace next time.
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> to unsubscribe from this list send an email to
> kdevelop-devel-request at kdevelop.org with the following body:
> unsubscribe »your-email-address«
In the garage of life there are mechanics and
there are drivers. Mechanics wanted!
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel