This is the mail archive of the
mailing list for the Cygwin project.
RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6
- From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder at niaid dot nih dot gov>
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Mon, 29 Sep 2014 21:23:16 +0000
- Subject: RE: [ANNOUNCEMENT] Updated: bash-4.1.13-6
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 54265593 dot 3030307 at byu dot net>
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
Disclaimer: Statements made herein are not made on behalf of NIAID.