https://bugs.winehq.org/show_bug.cgi?id=54661
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|8490c43f38e306fef7b5fed3ffc |77fdfdb8ef09153bf0adbfa6226 |b256efd73af58 |b6477b4dd0702
--- Comment #6 from François Gouget fgouget@codeweavers.com --- (In reply to Hans Leidekker from comment #4)
(In reply to François Gouget from comment #3)
So I could point at the commit that introduced the tests but the one I pointed to is the one that will cause 32-bit Windows applications to fail.
Most likely they would already fail since the dll was a stub.
I guess that's a fair point. Unlike our tests they probably stop on all SCardAccessStartedEvent() errors, not just on SCARD_E_NO_SERVICE. So getting that, SCARD_F_INTERNAL_ERROR (stub), or SCARD_E_INVALID_PARAMETER (current code) probably makes no difference to them. I'm updating the regression SHA1 then.
[...]
Now if the plan is to not support 32-bit code, then Wine should not provide a 32-bit winscard dll.
The plan is to support 32-bit code through Wow64 thunks.
Okay. What I meant is that then a pure 32-bit Wine build should not provide a 32-bit winscard dll. Currently this very basic command produces a crash in the tests:
./configure && make && ./wine dlls/winscard/tests/i386-windows/winscard_test.exe winscard
And running the 32-bit test in a 64-bit wineprefix crashes too: https://test.winehq.org/data/patterns.html#winscard:winscard