X-Spam-Check-By: sourceware.org Message-ID: <4522664E.30106@cygwin.com> Date: Tue, 03 Oct 2006 09:31:58 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060916 Fedora/1.5.0.7-1.fc4.remi Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.21 Forked background processes References: <4521AE57 DOT 9020007 AT cygwin DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Steve wrote: > Larry Hall (Cygwin cygwin.com> writes: > >>> file1.sh: >>> ----------------------------------------------- >>> #!/usr/bin/bash >>> >>> ./file2.sh & >>> >>> ------------------------------------------------ >>> >>> file2.sh >>> ------------------------------------------------ >>> #!/usr/bin/bash >>> >>> while [ 1 ] >>> do >>> val=`echo $val` >>> val=$((val + 1)) >>> echo $val >>> done >>> ------------------------------------------------ > > Thanks for your response. I'm still running into this with 1.5.21. The > background process has to be ran from a script, as in the example I provided > above. If you kick the script from the command line, this problem does not > occur. If you run the example above with ./file1.sh, you should see the > problem. I didn't run into this with DLL version 1.5.18. Here is the bash > and DLL versions of both: > > Problem DLL and Bash versions: > > $ bash --version > GNU bash, version 3.1.17(8)-release (i686-pc-cygwin) > Copyright (C) 2005 Free Software Foundation, Inc. > > Cygwin DLL version info: > DLL version: 1.5.21 > DLL epoch: 19 > DLL bad signal mask: 19005 > DLL old termios: 5 > DLL malloc env: 28 > API major: 0 > API minor: 156 > Shared data: 4 > DLL identifier: cygwin1 > Mount registry: 2 > Cygnus registry name: Cygnus Solutions > Cygwin registry name: Cygwin > Program options name: Program Options > Cygwin mount registry name: mounts v2 > Cygdrive flags: cygdrive flags > Cygdrive prefix: cygdrive prefix > Cygdrive default prefix: > Build date: Sun Jul 30 14:21:47 EDT 2006 > Shared id: cygwin1S4 > //////////////////////////////////////////////////// > > No Problem DLL and Bash versions: > > $ bash --version > GNU bash, version 3.00.16(11)-release (i686-pc-cygwin) > Copyright (C) 2004 Free Software Foundation, Inc. > > > Cygwin DLL version info: > DLL version: 1.5.18 > DLL epoch: 19 > DLL bad signal mask: 19005 > DLL old termios: 5 > DLL malloc env: 28 > API major: 0 > API minor: 132 > Shared data: 4 > DLL identifier: cygwin1 > Mount registry: 2 > Cygnus registry name: Cygnus Solutions > Cygwin registry name: Cygwin > Program options name: Program Options > Cygwin mount registry name: mounts v2 > Cygdrive flags: cygdrive flags > Cygdrive prefix: cygdrive prefix > Cygdrive default prefix: > Build date: Sat Jul 2 20:30:04 EDT 2005 > Shared id: cygwin1S4 > ////////////////////////////////////////////////////// > > I also tried Bash 3.00.16(11) with DLL version 1.5.21 and still had a > problem. I see this on several machines so it's not isolated to one. > > Thanks for your help and any info you can provide, I have tried this locally with 1.5.21 and bash 3.1.17-8 using the scripts you provided and don't see the issue you report. That's not to say that there isn't an issue. Only that I cannot reproduce it. Maybe it's worthwhile for you to review the output of 'cygcheck -srv' and see if something there catches your attention. If not, sending it to the list might spot something. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/