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 it with my own build (setupapi_crosstest.exe) which has only 2 failures). Both tests executables succeeded on my windows machine without any failures.
Attached is the log from both runs on wine.
I have no glue where the difference come from. I guess it has something todo with this commit http://source.winehq.org/git/wine.git/?a=blobdiff;f=dlls/setupapi/tests/pars... , which introduced the failing tests. But I couldn't run a regression test because my own compiled version didn't trigger the failures.
Any suggestions?
Cheers Rico
[Ricola@ricola build]$ ./wine ~/Desktop/setupapi_test.exe parser parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=1 parser.c:154: Test failed: file 1: Bad error 3758096384/3758096640 parser.c:156: Test failed: file 1: Bad error line 1/0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=5 parser.c:148: hinf=FFFFFFFF err=0xe0000002 line=3 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=1 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=3 parser.c:148: hinf=00127410 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=-1 err=0xe0000101 parser.c:233: hinf=00127410 ret=-1 err=0xe0000101 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:233: hinf=00127410 ret=0 err=0x0 parser.c:277: Test failed: wrong len 0 parser.c:284: Test failed: wrong len 0 parser.c:289: Test failed: wrong len 0 parser.c:277: Test failed: wrong len 0 parser.c:284: Test failed: wrong len 0 parser.c:289: Test failed: wrong len 0 parser.c:277: Test failed: wrong len 0 parser.c:284: Test failed: wrong len 0 parser.c:289: Test failed: wrong len 0 parser.c:277: Test failed: wrong len 0 parser.c:284: Test failed: wrong len 0 parser.c:289: Test failed: wrong len 0 parser.c:277: Test failed: wrong len 0 parser.c:284: Test failed: wrong len 0 parser.c:289: Test failed: wrong len 0 parser: 843 tests executed (0 marked as todo, 17 failures), 0 skipped. [Ricola@ricola build]$ ./wine ~/Desktop/setupapi_crosstest.exe parser parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=1 parser.c:154: Test failed: file 1: Bad error 3758096384/3758096640 parser.c:156: Test failed: file 1: Bad error line 1/0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=FFFFFFFF err=0xe0000100 line=0 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=5 parser.c:148: hinf=FFFFFFFF err=0xe0000002 line=3 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=1 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000000 line=3 parser.c:148: hinf=00127340 err=0x0 line=-559038737 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:148: hinf=FFFFFFFF err=0xe0000001 line=3 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=-1 err=0xe0000101 parser.c:233: hinf=00127340 ret=-1 err=0xe0000101 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser.c:233: hinf=00127340 ret=0 err=0x0 parser: 843 tests executed (0 marked as todo, 2 failures), 0 skipped. [Ricola@ricola build]$
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 failures) on wine. I checked it with my own build (setupapi_crosstest.exe) which has only 2 failures). Both tests executables succeeded on my windows machine without any failures.
Attached is the log from both runs on wine.
I have no glue where the difference come from. I guess it has something todo with this commit http://source.winehq.org/git/wine.git/?a=blobdiff;f=dlls/setupapi/tests/pars... , which introduced the failing tests. But I couldn't run a regression test because my own compiled version didn't trigger the failures.
Any suggestions?
Cheers Rico
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 res????.tmp file in .wine/drive_c/windows/temp
On my F10 box this also generates 15 failures, where 'make parser.ok' only shows 2 errors.
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 res????.tmp file in .wine/drive_c/windows/temp
On my F10 box this also generates 15 failures, where 'make parser.ok' only shows 2 errors.
Hi Paul,
Yes, this is exactly what I've done. I've also tried 'make parser.ok' and build my own cross test (mingw) which I've run in wine and which both show only 2 errors. The setupapi_test.exe is the extracted version from winetest.exe.
Cheers Rico
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 setupapi:parser'
- check the res????.tmp file in .wine/drive_c/windows/temp
On my F10 box this also generates 15 failures, where 'make parser.ok' only shows 2 errors.
Hi Paul,
Yes, this is exactly what I've done. I've also tried 'make parser.ok' and build my own cross test (mingw) which I've run in wine and which both show only 2 errors. The setupapi_test.exe is the extracted version from winetest.exe.
Cheers Rico
Hi,
just want to say problem found, the if (*need) *need = len; in SetupEnumInfSectionsA/W is wrong. I'll send a patch.
Cheers Rico
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 point. Just as a hint how to attack such beasts, if you encounter things like that again.
Regards, Michael Karcher
-
Michael Karcher -
Paul Vriens -
Rico Schüller