From: Qian Hong <fracting@gmail.com>
To: cygwin <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 12:03:00 -0000 [thread overview]
Message-ID: <CALd+sZT5eWWArH301hGhU+ZJsCst5O-bFyNoNrnUQMfOBnpk5w@mail.gmail.com> (raw)
In-Reply-To: <20150815112744.GA30028@calimero.vinschen.de>
Hi Corinna,
On Sat, Aug 15, 2015 at 7:27 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> 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 for the great help on irc. Also thanks for the test release.
I tested 32bit version of the test release, on both Wine and Windows7,
with both the xz command line and the test case writer.c attached in
original post. I can confirm both Cygwin Wine and Cygwin Windows works
now.
$ sha1sum cygwin1-20150815.dll
929cd14b16bad6e00f4f51f61b9105756cfab8f6 cygwin1-20150815.dll
$ file cygwin1-20150815.dll
cygwin1-20150815.dll: PE32 executable (DLL) (console) Intel 80386
(stripped to external PDB), for MS Windows
Will update if there is anything interesting.
--
Regards,
Qian Hong
-
http://www.winehq.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-08-15 12:03 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
2015-08-15 12:03 ` Qian Hong [this message]
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=CALd+sZT5eWWArH301hGhU+ZJsCst5O-bFyNoNrnUQMfOBnpk5w@mail.gmail.com \
--to=fracting@gmail.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).