Thread-safety issue in KConfig / KStandardDirs ?

Andreas Pakulat apaku at
Mon Jun 7 20:21:52 BST 2010

On 07.06.10 21:17:35, Oswald Buddenhagen wrote:
> On Mon, Jun 07, 2010 at 11:47:46AM -0300, Sandro Andrade wrote:
> > I'm facing again another possibly thread-safety issue in KConfig.
> > Since KConfig is not thread-safe and probably non-const methods are
> > being called from different threads, should I lock threads properly or
> > KConfig could somehow prevent this ?
> > 
> making kconfig's map accessors thread-safe would be relatively expensive
> for rather little gain in the general case, so i would say you need to
> do locking from the outside. what exactly would be your use case? the
> backtrace may just indicate a bug ...

The use is multiple parsing threads that ask the buildsystem support for
include dirs which needs to access the config in which the build-dir is


Chess tonight.

More information about the kde-core-devel mailing list