Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.programmer Subject: Re: Starting another copy of your own code Message-ID: <1991Mar14.125400.18953@sugar.hackercorp.com> Date: 14 Mar 91 12:54:00 GMT References: <1991Mar9.170859.4810@Sandelman.OCUnix.On.Ca> <06493.AA06493@babylon.rmt.sub.org> Organization: Sugar Land Unix -- Houston, TX Lines: 9 In article cg@ami-cg.UUCP (Chris Gray) writes: > The technique does not break on systems with caches, whereas the usual forms > of self-modifying code will. Sure. What if your newly-allocated seglist just happens to be sitting in a chunk of memory that an unloaded segment of code just vacated? -- Peter da Silva. `-_-' .