Don't unpatch an unloaded module. We verify if the original function address ...

Don't unpatch an unloaded module. We verify if the original function address is still valid
with a VirtualQuery call.

This fixes http://code.google.com/p/chromium/issues/detail?id=7701

Bug=7701
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=9929

[amit, 2009-02-17 23:21:13]

OK

[amit, 2009-02-17 23:21:19]

OK

[Dean McNamee, 2009-02-18 11:35:38]

http://codereview.chromium.org/21434/diff/1/2
File base/iat_patch.cc (right):

http://codereview.chromium.org/21434/diff/1/2#newcode217
Line 217: }
Shouldn't you set all of the functions to NULL here?

[Dean McNamee, 2009-02-18 12:48:46]

What if this area of the VA space was reused after the module was unloaded?  I
really think the underlying plugin issue should be fixed, as this is just a
bandaid (might as well have just wrapped it all around an catchall SEH handler).

On 2009/02/18 11:35:38, Dean McNamee wrote:
> http://codereview.chromium.org/21434/diff/1/2
> File base/iat_patch.cc (right):
> 
> http://codereview.chromium.org/21434/diff/1/2#newcode217
> Line 217: }
> Shouldn't you set all of the functions to NULL here?