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

List:       kde-pim
Subject:    Re: [Kde-pim] libkcal Segfault Proglems!
From:       Tobias Koenig <tokoe () kde ! org>
Date:       2005-01-09 12:57:00
Message-ID: 20050109125700.GB21681 () ghostdog ! localnet
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sun, Jan 09, 2005 at 02:35:56AM -0800, Andrew De Ponte wrote:
Hi Andrew,

> >You shouldn't use it in a thread, because it's not thread-safe...
> >
> Would making the class intense, which uses libkcal, a thread specific 
> data fix this problem? Or, can I just not use it within a thread at all.
Apart from missing locks for data access, libkcal send signals and uses
timers, which leads to conflicts in a thread.
Take a look at the documentation of QThread for more information.

Ciao,
Tobias
-- 
Separate politics from religion and economy!

["signature.asc" (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

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