3 Nov
2011
3 Nov
'11
10:10 a.m.
Alexandre Julliard julliard@winehq.org wrote:
What I mean is that if the old protection contains WRITECOPY, you won't be able to restore it correctly since you are going to make NtProtectVirtualMemory reject that.
I see. I think that a failure to restore WRITECOPY protection could be safely ignored. My investigation shows that a section with import thunks that would have WRITECOPY protection if it wouldn't contain import data has READWRITE protection after the DLL is loaded.
--
Dmitry.