[PATCH] Uninitialised variable produced by kconfig_compiler

[David Jarvie]

On Sunday 21 June 2009 20:07:58 you wrote:
> 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.

I attach a revised patch which takes care of the d pointer case.

-- 
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kcc.diff
Type: text/x-patch
Size: 777 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090621/dc201947/attachment.bin>