Re: [MiNT] XaAES / GEM memory issues

[Henk Robbers <h.robbers@chello.nl>]

"Konrad M. Kokoszkiewicz" wrote:

> I can. F_OS_SPECIAL allows the AESSYS process to access the application's
> private memory. It is a flag, which basically allows it to override the
> memory protection, and write to ANYWHERE, except free memory. This is very
> dangerous, and if you want an example, load Devpac 3.10 editor into N.AES,
> load a program into it and compile. You have very good chances to freeze
> your machine solid, because the Devpac editor somehow fools the AES to
> write into the area where system vectos are, and the AES, with its special
> privileges, obviously can do that, and does.

Hence my suggestion of the Pvaldate_vector system call.
This gives the AES the opportunity to deny this parameterblock and suspend or kill
devpac.

-- 
Groeten; Regards.
Henk Robbers.    mailto:h.robbers@chello.nl
                   http://members.ams.chello.nl/h.robbers/Home.html
A free multitasking GEM for MiNT: XaAES (heavily under construction);
Interactive disassembler: TT-Digger;  Experimental text editor: AHCX;