| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
| Message-ID: | <46040F99.C9722D77@yahoo.com> |
| Date: | Fri, 23 Mar 2007 12:34:17 -0500 |
| From: | CBFalconer <cbfalconer AT yahoo DOT com> |
| Organization: | Ched Research http://cbfalconer.home.att.net |
| X-Mailer: | Mozilla 4.75 [en] (Win98; U) |
| X-Accept-Language: | en |
| MIME-Version: | 1.0 |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: protecting program memory |
| References: | <1174648609 DOT 965097 DOT 60210 AT b75g2000hsg DOT googlegroups DOT com> |
| Lines: | 16 |
| NNTP-Posting-Date: | 23 Mar 2007 17:08:20 GMT |
| X-Complaints-To: | abuse AT teranews DOT com |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
tim DOT nicholson AT skyforcekent DOT com wrote: > > Is there an easy way to protect the memory used to store the program > op codes from a rogue memory write from within the application? .... Yes. Correct the program. Another possibility is to use a language with good runtime checking, such as Pascal or Ada, to enforce at least some of the corrections. -- Chuck F (cbfalconer at maineline dot net) Available for consulting/temporary embedded and systems. <http://cbfalconer.home.att.net> -- Posted via a free Usenet account from http://www.teranews.com
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |