From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin on Wine: changing buffer content immediately after aync write() to a pipe corrupts written result
Date: Sat, 15 Aug 2015 11:27:00 -0000 [thread overview]
Message-ID: <20150815112744.GA30028@calimero.vinschen.de> (raw)
In-Reply-To: <CALd+sZSJeQVmhtwfPSXxQtWTYfVvFh_ikxZL2p0Jo4thBwykuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hi Qian,
On Aug 15 19:11, Qian Hong wrote:
> Dear list,
>
> Recently we are investigating a Wine (Wine Staging) bug encountered by
> Cygwin/MSYS2, which also suggest a potential bug in Cygwin.
> [...]
thanks for the detailed report and your efforts to reproduce the issue.
As discussed on IRC, I'm going to use this for the release notes. The
proposed Cygwin fix is in the 2.2.1-0.1 test release I'm uploading right
now.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-15 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 11:12 Qian Hong
2015-08-15 11:27 ` Corinna Vinschen [this message]
2015-08-15 12:03 ` Qian Hong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150815112744.GA30028@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).