home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zephyr.ens.tek.com!uw-beaver!dylan
- From: dylan@cs.washington.edu (Dylan McNamee)
- Newsgroups: comp.sys.amiga.introduction
- Subject: Re: What is "enforcer" and "low memory"?
- Message-ID: <1992Aug13.214646.17578@beaver.cs.washington.edu>
- Date: 13 Aug 92 21:46:46 GMT
- References: <14250@mindlink.bc.ca>
- Sender: news@beaver.cs.washington.edu (USENET News System)
- Organization: Computer Science & Engineering, U. of Washington, Seattle
- Lines: 31
-
-
- If a program was written poorly, in exceptional (or normal!) cases,
- it may indirect through a null structure pointer. This means that the
- program "thinks" it is dealing with a proper structure, but it's
- really poking around in "low memory".
-
- One way to make sure that your own programs don't do this is to run
- enforcer while running them. Enforcer uses the MMU to un-map the low
- pages from a program's address space, and prints out alerts when these
- pages are touched. It is generally regarded as a good practice to make
- sure your program runs without making enforcer print anything before
- it is released as a product.
-
- Generally, if a released program (commercial or shareware or freeware)
- does cause enforcer warnings (called "enforcer hits" by programmers) it is
- a sign that the program isn't fully polished. Not Quite Ready For Prime
- Time.
-
- One reason people care about this is that programs that misbehave in this way
- can cause system crashes in unpredictable ways when many programs are running
- at once.
-
- hope this helps--
-
- dylan
- /L dylan mcnamee dylan@cs.washington.edu
- / L
- (o) L "Don't look at me...I didn't do it!" K. T. Clown.
- C (o) /
- /__ /
- \__/
-