Welcome Guest. Please Login or Register. Apr 1st, 2018, 04:03am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. We apologize Conforums does not have any export functions to migrate data. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
Data Execution Prevention
« Thread started on: Jul 8th, 2017, 8:40pm »
Carl has written this at the LB Community forum: "I think the solution is for Microsoft to make such things as DEP either trivially easy to deal with, or to eliminate them.". DEP is "trivially easy to deal with": don't execute code in memory that isn't executable!
When you allocate memory with VirtualAlloc you specify in the flProtect parameter whether you want the allocated memory to be executable (PAGE_EXECUTE) or not. If you don't, and subsequently try to execute code there (and DEP is enabled), it will fail.
This is not complicated. LBB is fully compatible with DEP, without any special measures being necessary, other than to allocate memory appropriately.
Logged