Am Sonntag, den 19.02.2012, 22:32 +0100 schrieb "Helmut Karlowski" <helmut.karlowski@ish.de>:XaAES can set the apid for the slb to the one of the caller, which fixes most issues, but it's still not a clean program and will kill the system sooner or later.
[...]
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 (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.
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.
Jo Even