[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kded crashes my system (X)
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-06-27 20:47:46
[Download RAW message or body]

On Sun, 27 Jun 1999, David Faure wrote:

> On Sun, Jun 27, 1999 at 10:24:59PM +0200, Simon Hausmann wrote:
> > On Sun, 27 Jun 1999, Dirk A. Mueller wrote:
> > 
> > > Mario Weilguni <mweilguni@sime.com> wrote:
> > > 
> > > > Don't use swapspace, that keeps the system alive. It seems the system 
> > > > is completly busy managing swapspace, it's not crashed.
> > > 
> > > Well, but there is no disk activity. In addition I can switch between
> > > consoles as normal, only all applications have stopped running.
> > > 
> > > I see here:
> > > 
> > > autoregistering KDE Helpcenter...
> > > Assert failure in kregfactories line 205
> > 
> > Looks like something went wrong with your binary registry file. Perhaps it
> > got corrupted on your system? Try deleting it (~/.kde/share/config/kregistry)
> > 
> This is the point where using a binary registry gets ... as bad as it is under
> Windows. What about handling errors better in the registry loading, and if
> anything fails, skip the loading and fall back on reading the ascii files
> (which we do anyway - if modification time differs) ?
> 
> I know, easy to say, not to do (the "<<" operator doesn't really allow good
> error checking !).

I fully agree with you.

Well, we can at least do some "minimum" handling by replacing the ASSERT
calls (like in line 205 in kregfactories.cc) with proper error handling
and read the registry in a "safe" way then (as you said it) , although I
admit that it's no real solution.

Hmmm... Is there any way to get rid of the operator way or to introduce
error handling with it? Perhaps something like with the >>= operators of
CORBA::Any ?

Ciao,
  Simon

--
Simon Hausmann       <hausmann@kde.org>
http://www.kde.org/  <tronical@gmx.net>

[prev in list] [next in list] [prev in thread] [next in thread]