Dmitry Timoshkov dmitry@baikal.ru writes:
The test initializers that call GetProcAddress() do write to the same section where the static buffer resides, which leads to the image section protection change.
That doesn't make the test invalid.
Alexandre Julliard julliard@winehq.org wrote:
The test initializers that call GetProcAddress() do write to the same section where the static buffer resides, which leads to the image section protection change.
That doesn't make the test invalid.
Correct, it makes it todo_wine. Shoudl I resend the whole set, or will you do a favour for me and mark the test as todo?
Dmitry Timoshkov dmitry@baikal.ru wrote:
The test initializers that call GetProcAddress() do write to the same section where the static buffer resides, which leads to the image section protection change.
That doesn't make the test invalid.
Correct, it makes it todo_wine. Shoudl I resend the whole set, or will you do a favour for me and mark the test as todo?
On the second thought I think that the test is really invalid, it depends on the linker to put both the static buffer and the changed data (API pointers) in the same page of the same section in a PE binary.
Dmitry Timoshkov dmitry@baikal.ru writes:
On the second thought I think that the test is really invalid, it depends on the linker to put both the static buffer and the changed data (API pointers) in the same page of the same section in a PE binary.
That still doesn't make it invalid. You can write to the variable if you want to make sure it's modified.
-
Alexandre Julliard -
Dmitry Timoshkov