https://bugs.winehq.org/show_bug.cgi?id=47198
--- Comment #102 from David Torok dt@zeroitlab.com --- The NtDebugActiveProcess process part of the issue is now properly fixed by 46b84e7a83beae7484e6daac16739a2b9238f68e upstream.
Just a reminder, the remaining issue is: Allocating a proper windows %gs segment and changing %gs on transitions. We already have a similar issue on ARM in the form of x18 collisions. (bug 38780) We can either wait for upstream to solve that and basically adopt the same for x86 or make something like that on our own for staging.
Since syscalls are labeled with -syscall in the spec files, now it's even easier than before to make a hack for this using forced +relays. However, for a proper solution to exist, there has to be an interface between all unix and windows code where we can put thunks like this. There has been good progress on that front (having a distinct barrier), but it's not there yet.
Maybe it's desirable to close this issue in favor of splitting it into "Wow64: distinct barriers between unix and windows code" or something similar?