This is the mail archive of the
mailing list for the Cygwin project.
Re: problems with bash
- From: "Michael A Chase" <mchase at ix dot netcom dot com>
- To: "morad m" <mekkim at hotmail dot com>,<cygwin at sources dot redhat dot com>
- Date: Tue, 12 Feb 2002 09:04:01 -0800
- Subject: Re: problems with bash
- References: <LAW2-F9414N69dStaJA00003d38@hotmail.com>
This is a general shell script debugging problem, probably not Cygwin
I'm a bit nervous about $a and $b not being quoted. If either is absent or
empty, the effects could be unexpected.
Try to eliminate some of the 2000 lines that aren't causing the problem.
"set -x -v" before the if might help you to see where the error is actually
If the script has more than a couple dozen lines, you should probably write
the script in Perl or Python. Just catching a couple problems like this
before they blow up will repay you the time it takes to learn either
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "morad m" <firstname.lastname@example.org>
Sent: Tuesday, February 12, 2002 08:38
Subject: problems with bash
> I have noticed one problem when using bash:
> In my script :
> if [ $a = $b ]; then
> (about 2000 lines of shell stuff here)
> Then bash fails with the following error:
> fork_helper: child died before initialization with win32 error 128
> fork: No more processes
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html