delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
Date: | Fri, 23 Mar 2007 15:34:38 -0400 |
Message-Id: | <200703231934.l2NJYcLZ027617@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp AT delorie DOT com |
In-reply-to: | <4604476A.28947.324D069D@gerritvn.gpvno.co.za> |
Subject: | Re: protecting program memory |
References: | <1174648609 DOT 965097 DOT 60210 AT b75g2000hsg DOT googlegroups DOT com> <4604476A DOT 28947 DOT 324D069D AT gerritvn DOT gpvno DOT co DOT za> |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> I certainly thought code would be protected, but it is not - I have > just tested it. What is the reason for that? DJGPP uses the traditional unix model whereby code and data segments overlap. Thus, the one key protection - segment flags - is bypassed. The second key protection - page tables - depends on your DPMI server whether it's offered or not.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |