Date: Tue, 15 Nov 2011 14:22:02 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: fork problem on latest cygwin CVS
Message-ID: <20111115192202.GB18893@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4EC12860 DOT 3050507 AT gmail DOT com> <20111114153109 DOT GA21295 AT ednor DOT casa DOT cgf DOT cx> <4EC13D23 DOT 8040705 AT gmail DOT com> <20111114171105 DOT GA22991 AT ednor DOT casa DOT cgf DOT cx> <4EC27F70 DOT 60102 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EC27F70.60102@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote:
>On 11/14/2011 6:11 PM, Christopher Faylor wrote:
>
>> FYI, the last thing any developer wants to hear after a major code
>> change is a generic "It's broke" report with no details and no way to
>> duplicate the problem.  A stack trace from a home-grown version of
>> cygwin1.dll is not a detail.  It's meaningless unless the addresses are
>> decoded.
>>
>> cgf
>
>Ok,
>rewinding to step 1
>
>I simplified the test case to a short one, involving just 1 make call,
>using your snapshot

Amazingly short.  Thanks very much!  I can duplicate this and will fix it.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple