Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 14 Feb 2002 12:28:43 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: wait_subproc failures in 2002-Feb-10 snapshot
Message-ID: <20020214172843.GA1576@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20020214172938 DOT GA1960 AT hp DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020214172938.GA1960@hp.com>
User-Agent: Mutt/1.3.23.1i

On Thu, Feb 14, 2002 at 12:29:38PM -0500, Jason Tishler wrote:
>Since upgrading to the 2002-Feb-10 snapshot (for the PostgreSQL fix),
>I have been getting the following transient error messages from my
>fetchmail daemon (i.e., NT service via cygrunsrv):
>
>      0 [proc] fetchmail 820 wait_subproc: wait failed. nchildren 1, wait 1000, Win32 error 6
>  30172 [proc] fetchmail 820 wait_subproc: nchildren 1, event[1] 0x14, pchildren[0] 0x1AE60000, events[0] 0x230, Win32 error 6
>  50549 [proc] fetchmail 820 wait_subproc: pid 2236, dwProcessId 2236, hProcess 0x14, progname 'C:\cygwin\bin\sh.exe'
>
>After the above occurs, fetchmail is wedged.  If I restart fetchmail, then
>it is OK for a while. However, it eventually hangs in the same way again.
>
>Any ideas of how to debug this further would be greatly appreciated.

Rebuild the DLL with --enable-debugging and you'll probably see that
someone is stomping on a handle.

I assume that this wasn't an issue with the previous snapshot?  If so,
it should be pretty easy to track down what caused the problem. There
hasn't been that much activity in cygwin lately.

cgf