This is the mail archive of the
mailing list for the Cygwin project.
Re: [OT] Wine + Cygwin: `script -e` exit status forwarding randomly return zero for non zero child process
- From: Qian Hong <fracting at gmail dot com>
- To: cygwin <cygwin at cygwin dot com>
- Date: Tue, 8 Sep 2015 01:13:57 +0800
- Subject: Re: [OT] Wine + Cygwin: `script -e` exit status forwarding randomly return zero for non zero child process
- Authentication-results: sourceware.org; auth=none
- References: <CALd+sZS6eHn8tUxCzB-JhGkfn2FUzg5dNKHwcY+ryBT-o=2DFw at mail dot gmail dot com> <20150903105549 dot GT23669 at calimero dot vinschen dot de> <CALd+sZRO9LbvQcQZ4PVf9Ge1e5Gu0kKTQkucm=YC68ENdkNNAA at mail dot gmail dot com> <20150907122836 dot GB20288 at calimero dot vinschen dot de>
- Reply-to: fracting at gmail dot com
Thanks again for the quick reply.
On Mon, Sep 7, 2015 at 8:28 PM, Corinna Vinschen
> Guys, no offense meant, but I'd really appreciate if you could peruse
> and refer to the original upstream Cygwin repo at
> This is what we're talking about in the first place so I'd like to stick
> to this, ok?
Oops, I'm so sorry, it's my mistake, it was just a lazy copy&paste
from bugzilla, not on purpose, won't happen again. Thanks for
> Ah, ok. What OS does Wine emulate here? Have a look at
> The terminate_thread_frees_stack flag is set to false for XP/2003 and to
> true for any newer OS. I guess this is a double-free because Wine's
> TerminateThread already freed the stack and Cygwin got the info it's
> supposedly running under XP/2003, so it tries to workaround the fact
> that TerminateThread on these systems didn't free the stack by themselves.
Wine emulates Windows XP here, I double checked Wine source code and I
can confirm Wine doesn't free the stack:
NtTerminateThread() -> abort_thread() -> terminate_thread()
Cygwin reports wincap as wincap_xpsp2 which is also correct here.
> we need to know what address ret=61005767 is refering to. addr2line would help.
As you point out, ret=61005767 is the call to VirtualFree() inside
After combine the information we have so far, I think the problem is
clear now. It's not Cygwin's fault, it's Wine's fault. Wine's
WaitForSingleObject() needs to wait long enough after the
TerminateThread() call, so the target thread has enough time to finish
the system cleanup and return correct exit_code before Cygwin call
VirtualFree to free the stack. But in our current implementation
Wine's WaitForSingleObject returns too early, it shouldn't return
before the system thread cleanup done, as a result there is a race
here. We are thinking of a solution in Wine. Thanks again for the
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple