Instead of https://gitlab.winehq.org/wine/wine/-/merge_requests/7815, for https://gitlab.winehq.org/wine/wine/-/merge_requests/7226, this only split the sync ops to a separate vtable and let objects delegate theirs to a separate object.
This starts using a event-like interface for most objects, leaving the decision regarding if/how to split sync themselves / integrate inproc syncs for later.
--
v8: server: Use an event sync for fd objects.
server: Introduce a new event sync object.
server: Redirect fd-based objects sync to the fd.
server: Add an operation to retrieve an object sync.
server: Move object grab/release out of (add|remove)_queue.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7848
For a 32bit DLL, dbghelp exports both the 32bit and the 64bit
variant of some APIs (eg. StackWalk, SymLoadModule...).
For a 64bit DLL, only the 64bit variant is implemented and
exported (the two names point to the same address in the export
table).
This patch:
- uses the same function for both names (as native does) in .spec file
for 64bit architecture
- removes the 32bit variant from 64bit compilation,
- adapts also the corresponding import:s in imagehlp from dbghelp.
This mostly fixes 64bit apps, getting eg "StackWalk" address with
GetProcAddress() and expecting a 64bit code path.
(reported & tested by Stefan).
Signed-off-by: Eric Pouech <epouech(a)codeweavers.com>
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8076