Date:	Wed, 30 Mar 94 11:15:06 -0500
From:	dj AT ctron DOT com (DJ Delorie)
To:	dridge AT MIT DOT EDU
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu, dridge AT MIT DOT EDU
Subject:	Re: Tricky Debugging Problem

> I'd like to say my code isn't the culprit, but everytime someone
> says this they are wrong.  What I would like is a way to catch pointer
> references into screen memory and into this buffer that are done by
> anything other than the couple of pointers that are suposed to be
> touching these areas.
> 
> Is there any good way to do this?

There's no good way, but there are ways.  Modify go32 so that you can
shut off the permissions on the page tables for those memory regions
(and back on again, of course) and it will fail any attempt to access
them outside of your areas.

There's also the chance that go32 itself has problems paging; we
normally try to avoid paging so we would normally miss these kinds of
errors if they exist.

DJ

- Raw text -