Re: [MiNT] Fwd: Re: marathon,was:Egale

["Jo Even Skarstein" <joska@online.no>]

On Mon, 20 Feb 2012 09:05:59 +0100, Helmut Karlowski  
<helmut.karlowski@ish.de> wrote:

> > > It's not only for marathon but to improve the general stability.
> >
> > I don't think these two statements are compatible ;) If this hack  
> > causes a
>
> It would kill the system immediately else.

Why? You are already catching it, but instead of allowing the application  
to continue you could kill it immediately.

> > (delayed) system crash, then it doesn't improve general stability at  
> > all.
> > Instead it could prevent the user from detecting the real cause of the
> > problem.
>
> The instability does not nessecarily come from the slb - there are  
> probably many other issues in marathon.

Ok, so the cause of the inevitable crash is not determined? That changes  
it. I thought the appl_init() from slb_init() was found to be the cause.

> > If calling the AES from slb_init causes problems, then XaAES should
> > immediately kill the application and display a warning. You are not
> > supposed to call the AES from slb_init anyway, so in this particular  
> > case
> > it's a matter of fixing the SLB.
>
> Let the user decide ;-)

The user will never know because the bug is silently accepted. So when  
(if) the system crashes due to this the user won't know why.

Jo Even