X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=NrMLLuVPWrGEUwSQfCNAXRVSwTVuA
	TJ/yJQjAkxzDejbHI7/wOZ+AgHNiIQPhnrbES/HLCeUDVaWDyN+VLjl0VkICkOLw
	VaHpQPG4g48eMgzBvAIJ+6qJe+N0Z6cBM+fMHnAIOEa89Zmg5RIPCNse8iWyeOwd
	8iUubsNndlvoYU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=gBX9Zy3eMcLNGTz3jLV8uj24sfU=; b=DJL
	gBjsajx5+ItyZpLRknhjnv/RMZO5gna+DK+6O33E/QqpwG+36KyCn5JY+UvgJWbw
	FNYc/MNxqhBE2a7jKbKZgvNBwPg/hszSOTFNB78UZqa36sV8e/qpmmEEfVlParbN
	GNXQcHVSG/LtLml8EueP8LNCKXkDKEunPDPdRey4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: nihtlsxway.hub.nih.gov
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgKAF3iKVScKEe0/2dsb2JhbABggw+BLoJ9y0uDIQIZdxYBA28JhAMBAQEDARIREVUCAQgNCwICBiACAgIdExUQAgQbEweIFAifA4oqlgIBF4EsjjARFiKCeDaBHQWPS4IaA5M7jWKDY4F0QIECAQEB
X-IPAS-Result: AhgKAF3iKVScKEe0/2dsb2JhbABggw+BLoJ9y0uDIQIZdxYBA28JhAMBAQEDARIREVUCAQgNCwICBiACAgIdExUQAgQbEweIFAifA4oqlgIBF4EsjjARFiKCeDaBHQWPS4IaA5M7jWKDY4F0QIECAQEB
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6
Date: Mon, 29 Sep 2014 22:52:41 +0000
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA20EC16178@MLBXV06.nih.gov>
References: <announce DOT 54265593 DOT 3030307 AT byu DOT net> <6CF2FC1279D0844C9357664DC5A08BA20EC15E2A AT MLBXV06 DOT nih DOT gov> <5429CF29 DOT 8030205 AT redhat DOT com>
In-Reply-To: <5429CF29.8030205@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id s8TMqwfl019433

Eric Blake sent the following at Monday, September 29, 2014 5:29 PM
>On 09/29/2014 03:23 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> Eric Blake (cygwin) sent the following at Saturday, September 27, 2014 2:14 AM
>>
>> Using the new version of bash, two scripts that I use have both started giving me
>> the following error message(s).
>>
>> /usr/bin/bash: error importing function definition for `BASH_FUNC_make-log'
>> /usr/bin/bash: error importing function definition for `BASH_FUNC_configure-log'
>> /usr/bin/bash: error importing function definition for `BASH_FUNC_prt-alias'
>
>These functions contain '-' in their name; that's a limitation of
>the downstream forked patch I applied early to get 4.1.13-6 out the
>door. Upstream solved it in a nicer manner, so you can once again have
>functions with '-' in the name. Please try again with the just-released
>4.1.14-7.

I understand that to mean that 4.1.14-7 will be able to export functions with '-' in
their names.

>> I was able to get rid of this by commenting out the functions (make-log,
>> configure-log, and prt-alias) and removing them from the list of functions being
>> set and exported in ~/.bashrc.  I rarely use these functions and would be unlikely
>> to use them in a subshell so that works as a solution.
>
>Having the function wasn't the problem, it was exporting it. You can
>still have the function even in 4.1.13-6, as long as you don't export
>it.

Changed to underscores.  All is well.

>> Another thing happening is that some scripts are now sometimes giving this error
>> message, but only when the problem function exports are not being exported.
>>
>> Segmentation fault (core dumped)
>
>Umm, that's not good. Can you please come up with a minimal reproduction
>formula? Which program is dumping core? Bash, or something else? Is it
>due to trying to execute the function that was not imported?

It wasn't reproducible, but a while after I sent my email various windows stopped
responding, I couldn't close them, the machine wouldn't shut down, and ended up
unplugging the machine so I could reboot.  Let's assume that something unrelated
to cygwin was going on.

>> Any hints about what I should look for to make export of my bash shell functions
>> reliable?
>
>Upgrading to the next version :)

Will do!

Thanks for all your help.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.