https://bugs.winehq.org/show_bug.cgi?id=47970
Andrew Wesie awesie@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie@gmail.com
--- Comment #10 from Andrew Wesie awesie@gmail.com --- (In reply to Zebediah Figura from comment #8)
Surprisingly it turns out that Windows itself lies about SegDs, i.e. it returns a fixed value for it in NtGetContextThread()/RtlCaptureContext() regardless of its actual value, so I ended up writing a patch mostly like the one you attached here. That doesn't mean that we necessarily want it like this upstream—lying about the thread context is not great even if Windows does it too—but I'm satisfied to put it in Staging, at least until it breaks something (and boy does it make me nervous...)
What is your concern with pushing it upstream if tests show that it matches behavior with 64-bit Windows?