delorie.com/archives/browse.cgi | search |
Newsgroups: | comp.os.msdos.djgpp |
From: | Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca> |
Subject: | Re: Interrupt handlers and page locking |
Message-ID: | <Pine.SGI.3.91.970401095017.24639D-100000@atmosp.physics.utoronto.ca> |
Nntp-Posting-Host: | chinook.physics.utoronto.ca |
Sender: | news AT info DOT physics DOT utoronto DOT ca (System Administrator) |
Mime-Version: | 1.0 |
Organization: | University of Toronto - Dept. of Physics |
In-Reply-To: | <33405CE3.AD6@ajusd.ml.org> |
Date: | Tue, 1 Apr 1997 14:58:19 GMT |
References: | <33405CE3 DOT AD6 AT ajusd DOT ml DOT org> |
Lines: | 17 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
On Mon, 31 Mar 1997, Edward Schlunder wrote: > > Also, in my program, I -know- I don't have some parts of the interrupt > handler code and data locked, yet I never get page fault errors. How do > I force a page fault if it is possible to happen? > Try loading lots of TSR's, and run your program under a debugger. The closer your machine gets to full memory, the more likely you get a page out. Also, you could try allocating lots of memory at the beginning of the program that you don't use. You might even want to temporarily take some RAM out of your machine... You get the idea. --------------- Peter Berdeklis Dept. of Physics, Univ. of Toronto
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |