Re: memory protection

[Konrad Kokoszkiewicz <draco@mi.com.pl>]

> Running this program (coolabah), produced the following crash:
> 
> pid 16 (THING): MEMORY VIOLATION: type=private AA=3067D0 PC=2D3582 BP=28E000
> pid  3 (AESSYS): MEMORY VIOLATION: type=free    AA=1AB15C PC=F8D12 BP=EA000
> pid  3 (AESSYS): Operating System Killed
> Fatal MiNT Error: adjust debug level and hit a key...
> FATAL ERROR: You must reboot the system.

Saying the memory protection works wrong I meant such events _exactly_.

> Now, maybe it was the AES's fault, but I'm not doing anything 
> particularly unsual
> in Coolabah (AFAIK), so I dont see why this should happen. I understand why if
> the AES is killed, MiNT might want to quit (no shell left) - but I would have
> thought that it would be much nicer if MiNT didn't report a fatal MiNT error...

Actually, if MiNT quits, it says "leaving MiNT"...

Konrad M.Kokoszkiewicz
mail:draco@mi.com.pl
http://www.orient.uw.edu.pl/~conradus

** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV, 25)
**************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.