Thread-safety issue in cmake support ?

Niko Sams niko.sams at
Mon Jun 14 17:28:59 UTC 2010

On Sun, Jun 13, 2010 at 16:09, David Nolden <zwabel at> wrote:
> 2010/6/12 David Nolden <zwabel at>:
>> 2010/6/12 Milian Wolff <mail at>:
>>> David Nolden, 12.06.2010:
>>> well, what you show up there is just what we proposed, only slightly different.
>>> You copy the editor contents in the ::run() method, while we'd do it before
>>> its done, i.e. directly in the foreground thread.
> One more related problem which makes the foreground lock the simpler
> way: We cannot do all the foreground stuff in the constructor of the
> parse-job, because additional parse-jobs are created locally from
> within the backgruond for the #included files (which we only know
> after preprocessing), and those also may require access to the
> foreground for editor-text-retrieval, highlighting, etc.
> Btw. I am working on porting the DUChain away from smart-ranges just now.
Cool! This is great!!


More information about the KDevelop-devel mailing list