Does testbot's MingW miscompile winmm:midi tests?

Joerg-Cyril.Hoehle at Joerg-Cyril.Hoehle at
Mon Sep 6 04:02:53 CDT 2010


on test.winehq, WinME systems always report 8 rc=MMSYSERR_INVALPARAM
errors.  However, when running a MSVC compiled binary (as found in
testbot job #4990), no such error occurs.

Paul Vriens wrote:
>I only see those 8 errors with the winetest executable from
> My own cross-compiled version is fine, no errors there.

Likewise, Octavian Voicu's machines saw no failure with the MSVC
binary, but constantly produce red color on testbot.

This could
 - Either be a bug in testbot's MingW (compilation or includes)?
   What's the difference between testbot compilation and Paul Vriens'?
 - Some weird memory corruption affecting only WinME?
 - a bug in my tests?

Those INVALPARAM errors happen since May. However my May-19 patch did
not change the tests that since fail, so it must be a side effect of
something else.
 1. dwBytesRecorded is left uninitialised, which may produce random
    results -- if it were used.
 2. dwOffset is now set to 0xDEADBEEF; previously uninitialised.
Yet that does not explain why MSVC's and Paul's cross compiled binary succeed.

Paul and I found a bug in the mingw includes once. Perhaps that's another instance?

How to proceed from here?
 Jörg Höhle

More information about the wine-devel mailing list