Thanks for the tip, but that didn't seem to have helped.
The registry setting CYGWIN_NOWINPATH=1 did not seem to affect the
environment as seen in bash.
The variable seems to be set:
bash-4.4$ set
...snip...
COMSPEC='C:\WINDOWS\system32\cmd.exe'
CYGWIN_NOWINPATH=1
...snip
but the path variable contains still all the common system locations:
bash-4.4$ echo $PATH
/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Program Files
(x86)/iis express/PHP/v5.3:/cygdrive/c/Program Files/Common Files/Mic
rosoft Shared/Windows Live:/cygdrive/c/Program Files (x86)/Common
Files/Microsoft Shared/Windows Live:/cygdrive/c/Program Files (x86)/Intel/
iCLS Client:/cygdrive/c/Program Files/Intel/iCLS
Client:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:...snip...
Manually overriding the PATH variable in bash did not help (presumably
because the offending DLL is already loaded):
bash-4.4$ export PATH=/usr/local/bin:/usr/bin:/bin
bash-4.4$ echo $PATH
/usr/local/bin:/usr/bin:/bin
bash-4.4$
bash-4.4$
bash-4.4$ ls
0 [main] bash (11276) C:\Cygwin\bin\bash.exe: *** fatal error -
cygheap base mismatch detected - 0x3C52410/0x36F2410.
This problem is probably due to using incompatible versions of the
cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
On 2/11/2018 2:42 AM, Doug Henderson wrote:
On 11 February 2018 at 01:18, Andreas Schiffler wrote:
Terminal (bash) fails with:
Error: Could not fork child process: Resource temporarily unavailable (-1).
DLL rebasing may be required; see 'rebaseall / rebase --help'.
{snip}
bash-4.4$ ls
1 [main] bash (6316) C:\Cygwin\bin\bash.exe: *** fatal error - cygheap
base mismatch detected - 0x3922410/0x3962410.
This problem is probably due to using incompatible versions of the cygwin
DLL.
{snip}
I do have another version of the cygwin dll file on the system (Plex
installation) but that never caused any issues in the past.
{snip}
The method I use is to define CYGWIN_NOWINPATH=1 before I start
cygwin. Actually, I set it in my Windows User environment so it is
always set for my user. You can find the old windows path as the value
of the environment variable ORIGINAL_PATH. Then, when necessary, I add
only the previous path components that I require back in my
.bash_profile. In my cases,My path looks like:
$ echo $PATH
/home/USER/bin:/usr/local/bin:/usr/bin:/cygdrive/c/Go/bin:/bin
In your case, you may have Plex in your path. Make sure any Plex
related directories are not in your cygwin path.
A Google (or similar) search for "CYGWIN_NOWINPATH" will find many
pages on cygwin.com and stackoverflow.com.
HTH
Doug
--
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