technically in the OS (unix model) when you exec a program you are
executing "self modifying code" because the program space and
the data of most machines are in shared spaces, or are assumed
to be.
There must be TLB and data and instruction cache adjustments
after reading any program text into memory and before trying to
execute it, or you have a problem. (at least allowances are made
for such at the end of reading and doing the load process)
At least from an architecural standpoint, you must deal with
code that gets loaded after the "program" runs in general on
any system, other than special standalone ones, perhaps.
Jim
Sean 'Captain Napalm' Conner wrote:
> It was thus said that the Great ben franchuk once stated:
> >
> > I have yet to see a good use for self-modifying code.
<snip>
>
>
> As far as I can recall, that was the *only* time I've ever done
> self-modifying code.
>
> -spc (And it seemed like a good reason at the time ... )
Received on Thu Jan 27 2005 - 12:22:46 GMT
This archive was generated by hypermail 2.3.0
: Fri Oct 10 2014 - 23:37:45 BST