Adding "write protect" with call instruction, removing "write protect" with return instruction.
|
Prev: Adding "write protect" with call instruction, removing "writeprotect" with return instruction.
Next: See and Enjoy Indian Girls Gallery.
From: Stefan Monnier on 29 May 2010 23:19 >> The only way this has a chance of working (on existing hardware) if >> for the minimum stack frame to be at least 1 page in size, and for the >> applications to run with write access to the memory management tables. > A (probably crazy) idea that came to me was to use ECC bit inversion > to indicate a special "word". (This assumes that inverting all the Can someone remind me why these kinds of "solutions" are better than the ones that have been used for the last few decades (i.e. bounds checking) which also have the advantage of actually really plugging those hole rather than just making them harder to use. Stefan |