DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=kmt3
	MGqiDDeCiFH//W0JdTTZl2Qjy1f/NpCO56IY4KzRlnGCwW9RXRpmDtPc01x/qmUH
	w7k/O5JlNjZ0Zqs1eVqR0oWfWNIK2V+2e6EYCCdMNDJtaMyFz2cZ6+vZxYLbik1Y
	M42CTiq/FJ+PWYGz4fRjgf9HQuJZ/FG/NFUDXew=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: bash-4.3.39-2
To: cygwin@cygwin.com
References: <announce.556EF85C.3000809@redhat.com> <20150604125154.712cbb6af2fc96c5a2306494@nm.ru> <560466C1.20709@redhat.com> <20150928173032.f0a3253c068c27c077a0e18d@inbox.ru>
From: Eric Blake <eblake@redhat.com>
Openpgp: url=http://people.redhat.com/eblake/eblake.gpg
Message-ID: <5609550E.5010100@redhat.com>
Date: Mon, 28 Sep 2015 08:56:14 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150928173032.f0a3253c068c27c077a0e18d@inbox.ru>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gf5XcbxQtIf9v593chdaXETFgMPAkqUFo"

--gf5XcbxQtIf9v593chdaXETFgMPAkqUFo
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 09/28/2015 08:30 AM, Mikhail Usenko wrote:

> But catching that bug (in upstream?) hasn't changed anything
> at least on my installation:

Okay, so it sounds like your issue is separate.

>=20
> ---%<---<cygwin-test.sh>---%<---
> #! /bin/bash
> bash -version | head -n1
> echo
>=20
> sender()
> {
>   echo -n  '\r\n' >&2
>   echo -ne '\r\n'

'echo -n' and 'echo -e' are non-portable (even in bash; because I can
use 'shopt -s xpgecho' to get POSIX-mandated behavior).  Use 'printf'
instead.


> receiver()
> {
>   t=3D""
>   while read t || [ "$t" ]; do
>     echo -ne ": \t"
>     od -A n -t x1  <<<"$t"
>   done  >&2
> }
>=20
>=20
> # implicit pipe
> receiver < <(sender)
>=20
> # explicit pipeline
> sender | receiver

Okay, I can see the disappearing \r even on a binary mount, so it
appears to be unrelated to the fix for text mounts.

Meanwhile, doing something like this (with a shorter sender):

# sender | od -An -tx1
\r\n\r\r\n\r\r\r\n 0d 0a 0d 0d 0a 0d 0d 0d 0a

shows that the pipeline is not eating the \r, but rather it appears to
be an issue in 'read'.  I'm still investigating, but thanks for the
recipe, as it gives me something to focus on.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--gf5XcbxQtIf9v593chdaXETFgMPAkqUFo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJWCVUVAAoJEKeha0olJ0NqQnAH/0PDs7CYf3e2S8z9joJ2U/mI
b/E8QmjG4n2v5+CfNjCl1cLf6LyHgaspxjMjjEyTVIsXhKOuo1lmdYBqfiuP+XaO
sE8cev32HuPnuQ9Cbp7ROw/3g1bxCtGIXEaDWwheLnQ7+dJ8yJ+DajJAXfvo9oSk
QJJlP+WsROX6gYWrwyF2SHryKp0S+IIT22uWOSoizSIpkqJeae1BxW7/rkLdRBDd
FRldsdgElIMJPT9/bI0pSKK4HNd6VbzBQJqEbwgIukxrp68jT5m1KdRjU249QiWn
SLgXNCZs/q53ky5lw+6pCnU/SM/JETvgLgMrqdj/LI3zcj5wN9ju/74TLl1BdSA=
=xLtS
-----END PGP SIGNATURE-----

--gf5XcbxQtIf9v593chdaXETFgMPAkqUFo--