X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Steve Subject: Re: 1.5.21 Forked background processes Date: Wed, 4 Oct 2006 18:24:21 +0000 (UTC) Lines: 30 Message-ID: References: <4521AE57 DOT 9020007 AT cygwin DOT com> <4522664E DOT 30106 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes 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 sbcglobal.net> writes: > Hello again, > > This is what I managed to confirm so far by using snapshots: > > Snapshot 2006-03-09 - Problem does not exist. > Snapshot 2006-03-18 - Problem exists > > So it looks like this problem arose between 03/09/06 and 03/18/06. Looking at > the change logs in between this time shows what looks like process forking > changes (See change log for 3/13/06) although I haven't tried this snapshot > yet. > > Thanks, > ->Steve > > Hello All, So, I've isolated this problem to snapshot 03-13-06. This is where I first start seeing this ugly issue. I haven't had a chance to debug it yet but I'm guessing the change log for this snapshot might tell us something right off thhe bat. (http://cygwin.com/snapshots/winsup-changelog-20060309-20060313) Thanks for your attention, ->Steve -- 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/