From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19798 invoked by alias); 9 Sep 2016 16:35:34 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 21861 Received: (qmail 7363 invoked from network); 9 Sep 2016 16:35:34 -0000 X-Qmail-Scanner-Diagnostics: from mailout4.w1.samsung.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(210.118.77.14):SA:0(-1.1/5.0):. Processed in 1.174899 secs); 09 Sep 2016 16:35:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f4-f79cb6d000001359-c6-57d2e4c6d13e Date: Fri, 09 Sep 2016 17:35:15 +0100 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: zsh heredoc crash Message-id: <20160909173515.4cb8392e@pwslap01u.europe.root.pri> In-reply-to: <25855010.qczLe9GZ8n@kdudka-nb> References: <25855010.qczLe9GZ8n@kdudka-nb> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: quoted-printable X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t/xy7rHnlwKNziyTclix8mVjA6MHqsO fmAKYIzisklJzcksSy3St0vgypg1fRVrwUXWii3NZ1kbGA+xdDFyckgImEgc/7qeCcIWk7hw bz1bFyMXh5DAUkaJD7eOs4EkhASmMUnsfpgNkTjNKDF1WhMLhHOGUeLxtIXsIFUsAqoSy37e AxvFJmAoMXXTbEYQW0RAVGL5is1gNcICchLXv64Aq+EVsJc49rwDLM4poCOxdvYeFohtJRJz fk0C6+UX0Je4+vcT1Hn2EjOvnGGE6BWU+DH5Hlg9s4C6xKR5i5ghbG2JJ+8usELMUZe4cXc3 +wRG4VlIWmYhaZmFpGUBI/MqRtHU0uSC4qT0XEO94sTc4tK8dL3k/NxNjJBw/rKDcfExq0OM AhyMSjy8G3ZfChdiTSwrrsw9xCjBwawkwqv1ECjEm5JYWZValB9fVJqTWnyIUZqDRUmcd+6u 9yFCAumJJanZqakFqUUwWSYOTqkGxgbVWRlNm6OieNlyrq/a1dNTN61V67pIyaqq8mBb/aZH Wb/E37FWPqmfpyO/jOdozONtsgvtHks9unA2o8H7RdqiGecCPS7cvqd7++uSq/W3TgkvM6zX XpA//ZJUBeOeSYYVZ05dvcTQXlsZ/v/Nh5PR76yOceWv7PT4vGPxLPkzLNNu7/XYkaXEUpyR aKjFXFScCADdY2k6YwIAAA== On Fri, 9 Sep 2016 16:33:19 +0200 Kamil Dudka wrote: > On Friday, September 09, 2016 10:00:54 Paulo C=C3=A9sar Pereira de Andrad= e wrote: > > ---8<--- > > #!/usr/bin/zsh > >=20 > > cat >> /tmp/try < > export A=3D"$(tr '\n' ' ' < > content > > BLDARC)" > > EOF > > ---8<--- >=20 > I was not able to make upstream zsh 5.0.2 crash with the above reproducer. >=20 > The bug seems to be introduced with the following commit: >=20 > https://sourceforge.net/p/zsh/code/ci/c0d01a6f >=20 > ... and fixed with the following commit: >=20 > https://sourceforge.net/p/zsh/code/ci/c6c9f5da That's the underlying bug Paulo is talking about, yes (zsh-workers/34322). pws