Fix bad restore of the protection flags for memory pages when finding real code for hooks

[dcristoloveanu]

Fix bad restore of the protection flags for memory pages when finding real code for hooks. There were several issues:

• The address passed to the VirtaulProtect call that restores the protection flag could be different than the address originally used to set the page to EXECUTE_READ. This is due to the fact that pCode could be modified between the 2 calls.
• VirtualProtect only returns the old protection flag for the first page. So, should the protected area span 2 pages (highly unlikely but still possible), the second and potentially subsequent pages would have a possibly wrong protection flag restored
• The 64 bit version of the code did not call FindRealCode recursively (unknown why)
• The protected memory area was not big enough in some of the cases

The solution is to have 2 wrapper functions to protect and restore a memory area, which would account for walking multiple pages, saving the proper protection flag to be used when restoring.

[mattdurak]

3

looks like this is now 7 below... #Resolved

[dcristoloveanu]

Fixed

[mattdurak]