Crash in ~KApplication (was Re: Crash on exit, seemingly caused by netacces)

Klas Kalass klas.kalass at
Mon Jun 3 20:42:29 BST 2002

Am Sonntag, 2. Juni 2002 22:37 schrieb David Faure:
> On Saturday 01 June 2002 20:21, Klas Kalass wrote:
> >
> > I think the following happens:
> > On exit, the destructors are called, destructing KGlobals::_instance on
> > the way. When the kapplication destructor is done, all objects are
> > automatically deleted and in AuthDataList destructor the cached Data
> > shall be purged, but to check for the existance of the CacheDaemon a
> > KDEsuClient needs to be created which needs KGlobal::_instance in its
> > constructor to get the current locale.
> This "I need to create something upon destruction" scheme looks wrong to
> me. If this AuthDataList stuff has to be cleaned up, I assume it means it's
> been used previously, so why doesn't it keep the KDEsuClient around, when
> doing that, in order to reuse it upon destruction?

I am not sure about security implications: The KDEsuClient opens a socket in 
the constructor and that one would be around until AuthDataList is destroyed.  
If noone screems "NO" I will make a patch during LT and post it as soon as I 
am back online, hopefully well tested.

> Disclaimer: this is just a wild guess, I know nothing of AuthData*,
> CacheDaemon nor KDEsuClient.
me too ...


More information about the kde-core-devel mailing list