[Bug 52159] 64-bit cygwin gdb.exe and python3.8.exe fail to run

[WineHQ Bugzilla]

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

Zeb Figura <z.figura12 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |z.figura12 at gmail.com

--- Comment #3 from Zeb Figura <z.figura12 at gmail.com> ---
(In reply to Joel Holdsworth from comment #2)
> Are we saying that the stack bug and this bug are really bugs in Cygwin?
> 
> Of course in principle, Wine ought to run and piece of Windows software -
> even if it is buggy.
> 
> However, in practice, isn't it Cygwin's fault for reallocating the stack,
> and leaving stale pointers in ExceptionList?

No, Cygwin is fine here. The TIB list isn't supposed to be used on x86_64 at
all; we use it because we can't easily generate SEH exception information.

> And isn't it Cywin's fault for assuming the Windows dlls will never step the
> stack pointer over the guard pages?

No, that's part of the ABI; you're supposed to touch the guard pages first. The
default stack on Windows is also split into reserved and committed portions; we
just don't do that on Wine for some reason (possibly this one).

> Maybe one day these things could be handled in Wine, but for now, perhaps it
> would be better to make fixes for Cygwin.
> 
> Also the cygwin FAST_CWD code making assumptions about Windows executable
> code.

That on the other hand is something Cygwin shouldn't do.

Although, if I had to take my pick, I'd like Cygwin to stop abusing alloca() as
in bug 47812.

-- 
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.