Re: GEM and memory protection

[Julian Reschke-FJR010 <Julian_Reschke-FJR010@email.mot.com>]

Christof.Donat@student.uni-ulm.de%INTERNET wrote:
> 
> Hi all
> 
> > Well. Programs should use globally accessible memory for the AV
> > protocol,
> > and Gemini, the first program to implement that protocol certainly does.
> >
> > If other programs fail to do it properly, why not set the program flags
> > just for them, instead of disabling MP for all GEM programs?
> 
> Because Gemini doesn't handle wrong Software correctly. If Software sends
> a protected string via AV to GEMINI, GEMINI will be killed. To prevent that
> Gemini should hook into the SIGSEGV Signal and set a flag there. When a
> Message arrives the flag should be cleared. Then you try to access the
> Memoryblock. If the Flag is set afterwards the Memory was protected. You
> can display an allertbox.
> 
> I know, that it is not Gemini's fault, but why not making it better? BTW
> I have not hered of any Desktop that does that though I have written that in
> a Newsgroup a few months ago. Maybe I've missed something...

Well, that's certainly a good idea.

BTW; it would also be a good idea when -- on a protection violation -
the kernel would also display the process name of the owner of the
memory block that the process whas trying to access (if available).

Regards, jr