From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80353 invoked by alias); 13 Jan 2017 20:15:51 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 80236 invoked by uid 89); 13 Jan 2017 20:15:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=dumped, aborted, Aborted, codespunk X-HELO: mail-pf0-f178.google.com Received: from mail-pf0-f178.google.com (HELO mail-pf0-f178.google.com) (209.85.192.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Jan 2017 20:15:41 +0000 Received: by mail-pf0-f178.google.com with SMTP id 127so35550619pfg.1 for ; Fri, 13 Jan 2017 12:15:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:reply-to:references:to:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=/VSZeip/O3BtQEg0Yk+xghkc1suzZUH+C83iZNAKTOc=; b=F0f3sPEyNVb4YVJ2YAt4/bYApqqz8hanTdRq5GaDrPGLBN1CEQUPUdEq0ID/EZfUg5 LFEy4VsW1KVVcChA8Pp0psW5esI5QhR1YZ8wkfCL8+u65Gli8M4HVfIe9CR+9SsHGLOX pHomJbqTxCz8x0ByfL7u32LlxYAvXQhX5tNPkB5FnwzPiWPrPCf392xXfUgwalFJMwAF kIJ3L5GXxRnxU8Oq41ba/9NBkeOmiuFkJauHH/asjIgs/JyMB8JPIC5IRYEaWdAVKiQk 5WSA45LKACoKIG1U1FpTEse9WHPgDLl5U1vCa1QSTH63I03GgXHfjfS8lOQBw0rN/jGq 09eg== X-Gm-Message-State: AIkVDXI/7x6jM+9+MKk7mtqevLpOFQE5Z5L1WXRVJtXUYI/QzSKQbIOD5B936rRMvskdgw== X-Received: by 10.98.93.152 with SMTP id n24mr24443530pfj.107.1484338539232; Fri, 13 Jan 2017 12:15:39 -0800 (PST) Received: from [10.0.1.127] (ip72-209-49-95.ri.ri.cox.net. [72.209.49.95]) by smtp.gmail.com with ESMTPSA id c15sm31137386pfd.36.2017.01.13.12.15.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Jan 2017 12:15:38 -0800 (PST) Subject: Re: Bash declare built-in regression loses array quotations Reply-To: codespunk+cygwin@gmail.com References: <587931C1.5060509@gmail.com> To: cygwin@cygwin.com From: "Matt D." Message-ID: <5879356A.9070506@codespunk.com> Date: Fri, 13 Jan 2017 20:15:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <587931C1.5060509@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-01/txt/msg00153.txt.bz2 While my simple test passed, I am now experiencing runtime assertions with Cygwin. These assertions occur on 2.6.1-1 and the alternatively available 2.6.0-1: assertion "(s - envblock) <= tl" failed: file "/home/corinna/src/cygwin/cygwin-2.6.1/cygwin-2.6.1-1.i686/src/newlib-cygwin/winsup/cygwin/environ.cc", line 1242, function: char** build_env(const char* const*, WCHAR*&, int&, bool, HANDLE) /c/data/workspaces/remote/plugins/shared/scripts/plugin.sh: line 64: 8448 Aborted (core dumped) /usr/local/lib/codespunk/scra.exp --p "$p" "bin/$plugin.jar" "$user@$host:$path/other/plugins/$plugin.jar" assertion "(s - envblock) <= tl" failed: file "/home/corinna/src/cygwin/cygwin-2.6.1/cygwin-2.6.1-1.i686/src/newlib-cygwin/winsup/cygwin/environ.cc", line 1242, function: char** build_env(const char* const*, WCHAR*&, int&, bool, HANDLE) /c/data/workspaces/remote/plugins/shared/scripts/plugin.sh: line 64: 13920 Aborted (core dumped) /usr/local/lib/codespunk/scrb.exp $h --u "$u" --p "$p" "chmod 660 $path/other/plugins/$plugin.jar" This bug is SEVERE and I can no longer perform any builds with these assertions. The Cygwin installer does not appear to provide a working version for me to roll back to. Please advise. I cannot get any work done with in this state. Matt D. On 1/13/2017 3:00 PM, Matt D. wrote: > I updated yesterday to the latest Cygwin x86 release which included an > updated Bash 4.4.5(1). This release changes the default behavior of the > built-in 'declare' command which is causing scripts which relied on this > functionality to break. > > The following test will illustrate the change: > declare -A list > list[a]=1 > list[b]=2 > list[c]=3 > declare -p | grep list= > > On Bash 4.4.5(1) the output is: > declare -A list=([a]="1" [b]="2" [c]="3" ) > > Previously the result was: > declare -A list='([a]="1" [b]="2" [c]="3" )' > > I can confirm that this has always been the expected output when running > this command on Cygwin and Linux. I run CentOS which does not track the > latest Bash release and I don't know the procedure to check whether this > is an upstream regression or not. > > I have rolled back to Bash 4.3.48-8 which has restored the previous > functionality. > > Please advise. > > Matt D. -- 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