Pavel Troller <[EMAIL PROTECTED]> writes: > This page really is NOT executable. So, why the workaround has been activated > just for one page (6d4d0000 - 6d4d1000) and not for the other ones, where it > also should be ? Why this new page has not been worked-around ?
Because the app exception handler ignores the exception instead of propagating it. That's broken IMO, but it would certainly be possible to unprotect a larger range on the first fault. -- Alexandre Julliard [EMAIL PROTECTED]
