From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e80a1497a689d8a5 X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: Ada GC (was Re: Ammo-zilla) Date: 1999/11/06 Message-ID: <801fdt$ht8$1@nnrp1.deja.com>#1/1 X-Deja-AN: 545197153 References: <38120FAF.945ADD7D@hso.link.com> <7uutgd$87h$1@nnrp1.deja.com> <19991024.18033546@db3.max5.com> <38189268.43EB150F@mail.earthlink.net> <86ogdjtdwz.fsf@ppp-115-70.villette.club-internet.fr> <7vadsp$8q61@news.cis.okstate.edu> <1999Oct28.221910.1@eisner> <7vb3c4$8a21@news.cis.okstate.edu> <7vhg2n$7ht$1@nnrp1.deja.com> <7vkjea$b34$1@nnrp1.deja.com> <7vncgr$bpg$1@nnrp1.deja.com> <7vqd45$iiq$1@nnrp1.deja.com> <7vvroo$grr$1@nnrp1.deja.com> X-Http-Proxy: 1.0 x25.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Sat Nov 06 14:53:49 1999 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I) Date: 1999-11-06T00:00:00+00:00 List-Id: In article , "Vladimir Olensky" wrote: > It just never come to my mind that someone (one the client's > side) could try to do something (using unchecked conversions ) > for anything that is behind that protection wall (for me it > is a crazy idea). I guess Vladimir that you have solved the problem that has eluded everyone else in the field, namely how to be absolutely sure that your program is free of errors. We are not talking about DELIBERATE errors here, but for instance of a simple error like using unchecked conversion to do low level buffer copying, and getting the bounds wrong. > As a matter of fact I do not see the way how one can > penetrate in reality through hardware memory protection wall > directly using pointer arithmetic. You are assuming that it is indeed possible to provide the necessary memory protection between collected and non-collected domains. First, my point was about systems where this is not possible. Second: most systems are in practice in this category! > Generally there could be many approaches to increase safety. > One of the nice ones (for me) is to use notion of safe and > unsafe modules/packages as in Modula-3 and do not allow any > unsafe operations in safe packages. But as we are discussing this segregation in what packages are allowed to do is not helpful at all in this case in the absence of the ability to build data allocation firewalls at the hardware level (something that is often not possible, both in embedded systems -- which often lack such memory protection hardware -- and in higher level systems running on top of standard OS's, which lack this kind of capability). Sent via Deja.com http://www.deja.com/ Before you buy.