X-Recipient: archive-cygwin@delorie.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=KsWRbpriuuSiiUeaRk5o2hlU1X1EC
	XaB1DYJi3Jxv5+qRx66MhleAD5bwbKKITB6JAlhySEpFOihbLeae0/Fjk5AyGWFv
	HBJlYI6WE7l7dapxmin3ITSmi2mFHnM2mvz3WP4tSRRSjtDt7QrOpxLxYNb7Rvp4
	nowp93ed4lgmwg=
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=O6YknNDHZX71laHXUggneRi89Oc=; b=u4U
	eu/N+5tZfivrweznUpAzUO0IjuVThV813wFNkrB5pVeSoAcL/HurcDoZgZVmAMBQ
	S9N271c85FlSIAtoFb1WmctVTNN+xg/XMnNJBsyEl0KyTKY81lS62PHQiWBbBQUE
	7/80B59X5tuXNhSH07SNVpzkXGmgNu71Il/OLv04=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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: nihtlsxway5.hub.nih.gov
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMFAEbNKVScKEex/2dsb2JhbABghD2Cfc5rAhmBEwEDeIQEAQEEEhERVQIBCBoCBiACAgIdExUQAgQbEweIHJ8OiiqWAQEXgSyOQTiCeDaBHQWRZQOhHYNjgjSBAgEBAQ
X-IPAS-Result: AvMFAEbNKVScKEex/2dsb2JhbABghD2Cfc5rAhmBEwEDeIQEAQEEEhERVQIBCBoCBiACAgIdExUQAgQbEweIHJ8OiiqWAQEXgSyOQTiCeDaBHQWRZQOhHYNjgjSBAgEBAQ
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6
Date: Mon, 29 Sep 2014 21:23:16 +0000
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA20EC15E2A@MLBXV06.nih.gov>
References: <announce.54265593.3030307@byu.net>
In-Reply-To: <announce.54265593.3030307@byu.net>
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 s8TLNYcf013205

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'

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.

What makes this strange is that I have other shell functions that are defined in
~/.bashrc and exported.  They have not shown up in the error messages.  As it
happens, the problem functions are the last 3 on the export list.  However,
adding another function to be exported doesn't cause a new error message for
just one function that is now at the end of the export list.

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)

Any hints about what I should look for to make export of my bash shell functions
reliable?

Thanks,

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

