1.1 --- a/sourcehook/sh_pagealloc.h Fri Nov 09 06:23:08 2007 +0000
1.2 +++ b/sourcehook/sh_pagealloc.h Fri Nov 09 21:14:37 2007 +0000
1.3 @@ -3,9 +3,6 @@
1.4
1.5 # if /********/ defined _WIN32
1.6 # include <windows.h>
1.7 -# define SH_MEM_READ 1
1.8 -# define SH_MEM_WRITE 2
1.9 -# define SH_MEM_EXEC 4
1.10 # elif /******/ defined __linux__
1.11 # include <sys/mman.h>
1.12 # include <unistd.h>
1.13 @@ -23,7 +20,7 @@
1.14 If we alloc with malloc and then set the page access type to read/exec only, other regions returned by
1.15 malloc that are in the same page would lose their write access as well and the process could crash.
1.16
1.17 - Allocating one page per code generation session is usually a waste of memory and on some plattforms also
1.18 + Allocating one page per code generation session is usually a waste of memory and on some platforms also
1.19 a waste of virtual address space (Windows� VirtualAlloc has a granularity of 64K).
1.20
1.21