[Bug 49782] Elite Dangerous Horizons: crashes with wine64 5.16

[WineHQ Bugzilla]

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

--- Comment #8 from Paul Gofman  ---
(In reply to Brendan McGrath from comment #7)
> Is the reason for this change to potentially provide anti-cheat support?

If by anti-cheat support you mean a support for specific features for kernel
mode device drivers typically used by kernel mode anti cheats, then no, it is
not related. In some other aspects it might, to some extent.

The discussion of the ideas behind these changes probably falls far away from
the purpose of the bugtracker. I suppose the better places are #winehackers IRC
channel or [e-mail] mailing list.

Very briefly, Wine is going to have all the DLLs used by Win applications
directly built as PE (using mingw). The access to the host specific (native)
APIs is supposed to cross a well defined boundary, which boundary conceptually
(has no relation to kernel mode and other drivers) corresponds in some way to
user space / kernel space boundary on Windows. In this regard, "kernel space"
has absolutely nothing to do with kernel mode drivers (how Wine loads a device
driver is a separate story not related here) or how that looks like in the real
kernel on Windows, but interfacing from the user space libraries is supposed to
look as close as possible to how that is done on Windows (probably more close
when it is ntdll and not that close when it comes to some other libs requiring
host API interaction).

This helps a bunch of real cases covered by numerous bugs, including (but not
limited to):
- comparing in-memory image to the on disk image for system library (done by
some DRMs);
- hotpatching ("detouring") system functions (DRM related or not, e. g., for
implementing some sort of virtual file system). The dependencies between the
hotpatched functions should match Windows in order for that to work;
- a lot of fine details in system functions behaviour (on which apps, mostly
DRMs, sometimes depend) which is very hard to get right without separating the
native host part.

These are just the examples, there is more involved.