Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 26 Dec 2003 15:46:41 -0500
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Please try the latest snapshot -- it is close to cygwin 1.5.6
Message-ID: <20031226204641.GA46362839@hpn5170x>
Mail-Followup-To: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>, cygwin AT cygwin DOT com
References: <20031224152951 DOT GA34487383 AT hpn5170x> <20031223222816 DOT GA23935 AT redhat DOT com> <20031224152951 DOT GA34487383 AT hpn5170x> <3 DOT 0 DOT 5 DOT 32 DOT 20031224181524 DOT 007c21c0 AT incoming DOT verizon DOT net> <20031224232759 DOT GA12748 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031224232759.GA12748@redhat.com>
User-Agent: Mutt/1.4.1i

On Wed, Dec 24, 2003 at 06:27:59PM -0500, Christopher Faylor wrote:
> On Wed, Dec 24, 2003 at 06:15:24PM -0500, Pierre A. Humblet wrote:
> >At 11:59 AM 12/24/2003 -0500, Christopher Faylor wrote:
> >>On Wed, Dec 24, 2003 at 10:29:51AM -0500, Pierre A. Humblet wrote:
> >>>On Tue, Dec 23, 2003 at 05:28:16PM -0500, Christopher Faylor wrote:
> >>>> The subject says it all.
> >>>> 
> >>>> I'm hoping to release cygwin 1.5.6 shortly after Christmas.
> >>>
> >>>On WinMe the queue runner forked by the exim daemon still occasionally 
> >>>produces a popup indicating an error in Cygwin1.dll
> >>
> >>"a popup indicating an error".......?
> >>
> >>Not too helpful.
> >
> >It has happened once more, but differently. ps shows the child as defunct.
> >Sysinternals shows everything normal, pinfo exists in the child.
> >There is no fork failure, in fact the one I mentioned earlier is the only
> >one out of 17070 runs. 
> >
> >This time when I killed the daemon (just to see), I got
> > 330495 [main] exim 34658275 proc_subproc: couldn't get proc lock.
> >Something is wrong.
> > 330520 [main] exim 34658275 proc_subproc: couldn't get proc lock.
> >Something is wrong
> 
> If you have the time could you add some more debugging output to the
> failing cases that lead to this message and try running it with that?

I updated from cvs and noticed you had already added debug info.

CYGWIN_ME-4.90 hpn5170x 1.5.6(0.108/3/2) 2003-12-26 12:15 i686 unknown unknown Cygwin

-996371854 [main] exim 219879 proc_subproc: couldn't get proc lock. what 4, val 1628435976
-996369556 [main] exim 219879 proc_subproc: couldn't get proc lock. what 4, val 1628435976

Also, while running sysinternals I noticed to the exim daemon still had tty
related handles, despite setsid(). Ditto for inetd.

Pierre 

--
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/