How to Modify Executable Code in Memory
Article ID: 127904
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft Win32 Application Programming Interface, when used with:
- Microsoft Windows NT 3.51 Service Pack 5
This article was previously published under Q127904
Follow the steps in this article to create self-modifying code; that is, to
modify code pages while they are in memory and execute them there.
NOTE: Self-modifying code is not advised, but there are cases where you may
wish to use it.
Step-by-Step Example
- Call VirtualProtect() on the code pages you want to modify, with the
PAGE_WRITECOPY protection.
- Modify the code pages.
- Call VirtualProtect() on the modified code pages, with the PAGE_EXECUTE
protection.
- Call FlushInstructionCache().
All four steps are required. The reason for calling FlushInstructionCache()
is to make sure that your changes are executed. As processors get faster,
the instruction caches on the chips get larger. This allows more out of
order prefetching to be done. If you modify your code, but do not call
FlushInstructionCache(), the previous instructions may already be in the
cache and your changes will not be executed.
Additional query words: 3.50 4.00
Keywords: KB127904