Thread-safety issue in cmake support ?

David Nolden zwabel at
Sun Jun 13 14:09:47 UTC 2010

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.

Greetings, David

More information about the KDevelop-devel mailing list