Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 19 Jul 2001 11:31:00 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: fork on win95
Message-ID: <20010719113100.B5093@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <005101c11036$06368800$806410ac AT local> <20010719131210 DOT Y730 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010719131210.Y730@cygbert.vinschen.de>
User-Agent: Mutt/1.3.19i

On Thu, Jul 19, 2001 at 01:12:10PM +0200, Corinna Vinschen wrote:
>On Thu, Jul 19, 2001 at 07:34:34PM +1000, Robert Collins wrote:
>> Chris - feedback on your changes -
>> 
>> C:\CYGWIN\BIN\BASH.EXE: *** Couldn't allocate space for child's heap from
>> 0x8339
>> B000, to 0x8339EF08, Win32 error 487
>> 12808475 [main] BASH 93369 sync_with_child: child -111793(0x28) died before
>> init
>> ialization with status code 0x1
>> 12821630 [main] BASH 93369 sync_with_child: *** child state waiting for
>> longjmp
>> BASH: fork: Resource temporarily unavailable
>
>I have found another problem with the latest change which seems to
>be related to the CYGWIN=tty setting. I'm getting this (or a very
>similar output) when trying to logon from another box using ssh or
>when I start anything using `sh -c', both with CYGWIN=tty:
>
>$ sh -c ps
>
>      0 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle io_handle<0x16C>
>   8637 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle output_handle<0x170>
>  18431 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle output_done_event<0x138>
>  28342 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle ioctl_request_event<0x158>
>  38349 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle ioctl_done_event<0x15C>
>  48358 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle output_mutex<0x164>
>  58386 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle input_mutex<0x168>
>  68396 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle input_available_event<0x160>
>  78398 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle inuse<0x174>
>  88439 [main] ps 1108 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle io_handle<0x1B4>
>[...]
>The whole output is generated three times just with different handle
>values (stdin, stdout and stderr, probably). Then the normal `ps' output
>appears. Generally, the above ERROR_INVALID_HANDLE output appears,
>then everything works fine. That's also valid for the aforementioned
>ssh session. As usual nothing happens when started under strace control.

And, as usual, this would call for some debugging with gdb.

I can't duplicate this one either.

cgf