[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: memory protection

> |> Except Thing IS supposed to be MiNT-friendly. N.AES too. 
> |> Thing cannot even be started by N.AES correctly.
> Then why does it access memory it doesn't own?  That's still a bug.  If
> it's not bug-free (which will of course never happen for any non-trivial
> program) it should catch SIGSEGV and properly clean up in the handler.

As for that... it may be that additional protocols used by Thing (e.g. AV) 
aren't memory protection aware...

Konrad M.Kokoszkiewicz

** 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.