https://bugs.winehq.org/show_bug.cgi?id=55703
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #5 from Bernhard Übelacker bernhardu@mailbox.org --- (In reply to Zeb Figura from comment #4)
The application is buggy. It truncates and then sign-extends a stack pointer:
This can only work if the stack is allocated in the low 4G.
Looks like a81c53504a uncovers a row of buggy applications, when pointers grow above 32bit. Shouldn't wine try to mimic windows behaviour to stay below 4G if possible, like it did before a81c53504a?
I did check and this really does crash on Windows; it doesn't swallow an exception or anything.
How did you check this on windows, is there a simple way to force pointers above the 4G boundary to demonstrate it to the application developers?