Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Corinna Vinschen Date: Tue, 12 Dec 2000 10:12:56 +0100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" To: cygwin References: <3A35CBF2 DOT A2DCC748 AT unchance DOT net> In-Reply-To: <3A35CBF2.A2DCC748@unchance.net> Subject: Re: Bug in Cygwin-1.1.4 - cannot fork: No more processes MIME-Version: 1.0 Message-Id: <0012121012560A.00475@cygbert> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id EAA19212 Are you sure not having a second cygwin1.dll somewhere on your system? I suggest searching for it. Corinna On Tuesday 12 December 2000 07:55, u n c h a n c e wrote: > I have had the same problem. > > It happens every time I run bash 2.04 latest version. > > When first invoked after a reboot, bash exits with > this error: > > C:\BIN\BASH.EXE: *** Sig proc MT init failed > > 0 [unknown (0xFFE278D9)] ? 0 lock_pinfo_for_update: rc 0, > pinfo_mutex 0xFFFFFFFF, Win32 error 6 > > Subsequent invocations of bash succeed without > problem, but at random intervals when trying to > execute a command in the shell, the command will > fail and instead a message like this will occur > > C:\BIN\BASH.EXE: *** Sig proc MT init failed > > 0 [unknown (0xFFE2A047)] ? 0 lock_pinfo_for_update: rc 0, > pinfo_mutex 0xFFFFFFFF, Win32 error 6 > 0 [main] BASH 1000 sync_with_child: child -1869325(0x8C) died > before initialization with status code 0x1 > 42880 [main] BASH 1000 sync_with_child: *** child state waiting for > longjmp bash.exe: fork: No more processes > > The same command when executed again will then > succeed without problem and everything will be > fine until the next error like this. It happens > after maybe every 50 or 100 commands. > > I did not have this problem until quite recently. > I was able to run earlier versions of bash in > the same environment without observing this. > I am running Windows 98. It may have something > to do with the fact that I recently downloaded > the Windows NT port of COMMAND.EXE, though it > happens also if I run bash in the COMMAND.COM > shell. > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com