on 16/7/02 14:27, Philip Stortz at [EMAIL PROTECTED] wrote: > no, because the area that the buffer overflows into will likely be ram > in use by another application or more likely the os. basically what > happens is a bunch of code gets shoved into ram, by the software being > overflowed, into an area of ram the software in question likely has no > business accessing at all, and when the os or other software that's been > corrupted by having it changed in ram happens to branch into that area > of memory during "normal" execution the code gets run, just because it's > there and the software doesn't know the ram has been corrupted by a
Isn't this what "protected memory" management is supposed to prevent in *NIX? Eric. -- G-List is sponsored by <http://lowendmac.com/> and... Small Dog Electronics http://www.smalldog.com | Refurbished Drives | -- We have Apple Refurbished Monitors in stock! | & CDRWs on Sale! | Support Low End Mac <http://lowendmac.com/lists/support.html> G-List list info: <http://lowendmac.com/lists/g-list.shtml> Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive: <http://www.mail-archive.com/g-list%40mail.maclaunch.com/> Using a Macintosh? Get free email and more at Applelinks! <http://www.applelinks.com>
