[PATCH] Uninitialised variable produced by kconfig_compiler

Olivier Goffart ogoffart at bepointbe.be
Sun Jun 21 20:07:58 BST 2009

Le Sunday 21 June 2009, David Jarvie a écrit :
> If signals are defined, kconfig_compiler includes the mSettingsChanged
> member in the generated class, but it doesn't initialise it. Running
> valgrind shows an uninitialised mSettingsChanged variable being used in the
> tests in usrWriteConfig(). The attached patch fixes this. OK to commit?

Does this works when there is a d pointer?
It doesn't seems so.

More information about the kde-core-devel mailing list