[Bug 48208] Detect missing entry point errors

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48208

François Gouget <fgouget at codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from François Gouget <fgouget at codeweavers.com> ---
This case is now detected by TestLauncher and reported as a skip (see bug
31609). For instance:

rtworkq:rtworkq start - -
rtworkq.c:0: Tests skipped: missing entry point (details below)
| rtworkq_test.exe - Entry Point Not Found
| The procedure entry point CoGetApartmentType could not be located in the
dynamic link library ole32.dll.
09f0:rtworkq: 0 tests executed (0 marked as todo, 0 failures), 1 skipped.
rtworkq:rtworkq:09f0 done (0) in 0s

The two lines starting with "|" are extracted from the Windows critical error
dialog.

WineTest.exe instead arranges for CreateProcess() to fail so it does not get
the error information from the Windows critical error dialog (see bug 45032).
But it also skips the test and does not get stuck.

That means no extra log parsing or heuristic is needed to identify the missing
entry points, missing ordinals, and indirectly missing dlls. So I think this
issue is fixed.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.