[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] kernel 1.15.10b fragmentation
- To: MiNT mailing list <mint@fishpool.com>
- Subject: Re: [MiNT] kernel 1.15.10b fragmentation
- From: Guido.Flohr@t-online.de (Guido Flohr)
- Date: Tue, 2 Jan 2001 01:13:20 +0100
- In-reply-to: <aMail1.26b.20010101101508.2078917053@TT030>; from atari@bright.net on Mon, Jan 01, 2001 at 10:15:08AM -0500
- Mail-followup-to: Guido Flohr <guido@flohr.as>, MiNT mailing list <mint@fishpool.com>
- References: <aMail1.26b.20010101213157.1027100827@AB> <aMail1.26b.20010101101508.2078917053@TT030>
- Sender: owner-mint@fishpool.com
- User-agent: Mutt/1.2.5i
Hi,
On Mon, Jan 01, 2001 at 10:15:08AM -0500, Lonny Pursell wrote:
> A more generalized doc would be interesting indeed. The few times
> I've tested my system with MP, often results in a search and seek
> mission, trying to find the app at fault, cause often as you probably
> already know the app that gets killed, is often not the one to blame.
> Old or bad code from programs sending pointers to protected buffers
> and the like. I know I've done some tweaking and fiddling and
> wished there was more info to. I suspect often we who test MP
> end up fighting with common apps such as st-guide. ;-)
Proposal for new kernel function:
long MAccess (unsigned long address, unsigned long size,
short int mode);
This function should allow "innocent" applications to check a pointer
of foreign or otherwise dubious origin before it is being used. The
"mode" argument should hold a bit vector with the desired access method
(read, write or both).
Such a call would probably be a little more performant than installing a
signal handler for SIGSEGV.
Ciao
Guido