setupapi:parser - suspicious test results

Hi, concerning to http://test.winehq.org/data/tests/setupapi:parser.html there are some suspicious results for the test from 6-10. January. On my system (F10-x86_64) the setupapi:parser test (setupapi_test.exe) from the test site has 15 additional failures (17 failures) on wine. I checked

Re: setupapi:parser - suspicious test results

Rico Schüller wrote: Hi, concerning to http://test.winehq.org/data/tests/setupapi:parser.html there are some suspicious results for the test from 6-10. January. On my system (F10-x86_64) the setupapi:parser test (setupapi_test.exe) from the test site has 15 additional failures (17

Re: setupapi:parser - suspicious test results

Paul Vriens schrieb: Hi Rico, I guess the results on the website came from running the Windows winetest.exe? Could you try the following: - download winetest.exe - remove .wine (or move it away, use a different prefix, whatever) - run 'wine winetest.exe setupapi:parser' - check the

Re: setupapi:parser - suspicious test results

Rico Schüller schrieb: Paul Vriens schrieb: Hi Rico, I guess the results on the website came from running the Windows winetest.exe? Could you try the following: - download winetest.exe - remove .wine (or move it away, use a different prefix, whatever) - run 'wine winetest.exe

Re: setupapi:parser - suspicious test results

Am Sonntag, den 11.01.2009, 16:02 +0100 schrieb Rico Schüller: just want to say problem found, the if (*need) *need = len; in SetupEnumInfSectionsA/W is wrong. I'll send a patch. This looks like a typical problem valgrind is designed for. It should report an uninitialized memory read at that