X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 1 Aug 2010 15:14:35 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: elusive segfault on latest snapshots
Message-ID: <20100801191435.GB6255@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20100731172035 DOT GA3617 AT ednor DOT casa DOT cgf DOT cx> <962517 DOT 70320 DOT qm AT web25505 DOT mail DOT ukl DOT yahoo DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <962517.70320.qm@web25505.mail.ukl.yahoo.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Sat, Jul 31, 2010 at 05:40:27PM +0000, Marco Atzeri wrote:
>--- Sab 31/7/10, Christopher Faylor  ha scritto:
>
>> -0400, Christopher Faylor wrote:
>> >On Sat, Jul 31, 2010 at 08:25:42AM +0000, Marco Atzeri
>> wrote:
>> >>on latest snapshots after 2010-07-07, I am picking
>> random segfault
>> >>building or configuring several programs
>> >
>> >Does this mean that 2010-07-07 does not have problems?
>
>yes, it works fine
>
>> 
>> Actually, I'd be particularly interested in knowing if
>> 2010-07-18 has
>> the problem.
>
>yes, it has.
>
>> 
>> cgf
>> 
>
>It is very elusive and it does not happen all the time,
>just most of the time; every snapshot segfault in a 
>different point of the building and some time also
>the same snapshot behavior differently. 
>
>I guess is due to some type of race but no clue how to
>pin point it.

It's sort of a race but it's really more of an incredibly stupid thinko
on my part owing to the fact that I "optimized" some of the signal
handling.  I almost knocked myself with the head slap out when I finally
saw the simple problem.

This should be fixed in today's snapshot.

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