I do not have ubuntu/mmap protection here, could you/somebody try with a
address like 0x8.
I've run the attached test program on Windows XP SP3, Hardy Heron 8.04, and
a Debian 'Lenny' system for the memory range of 0x0 through 0x11.
The results were that on Windows XP, you get partial
On Montag 19 Mai 2008, Jeremy White wrote:
> > ntdll:info is a flaky test marked todo_wine that succeeds sometimes:
> > "info.c:822: Test succeeded inside todo block: Expected to read 0
> > bytes, got 0"
>
> Hardy seems to be the common variable for failures, and it seems as though
> an actual fai
Dan Kegel wrote:
> Thanks to everybody who responded to Jeremy's call
> to run winetest using the 'dotests' script at
>http://wiki.winehq.org/MakeTestFailures
>
> We now have 35 reports, and have some good data on
> which test failures are common. See the
> Most Common Failures section at the
> ntdll:info is a flaky test marked todo_wine that succeeds sometimes:
> "info.c:822: Test succeeded inside todo block: Expected to read 0
> bytes, got 0"
Hardy seems to be the common variable for failures, and it seems as though
an actual failure reading from location 0x1234 is the trigger.
(The
Thanks to everybody who responded to Jeremy's call
to run winetest using the 'dotests' script at
http://wiki.winehq.org/MakeTestFailures
We now have 35 reports, and have some good data on
which test failures are common. See the
Most Common Failures section at the bottom.
Here's what it says ri
