This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: elusive segfault on latest snapshots
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 1 Aug 2010 15:14:35 -0400
- Subject: Re: elusive segfault on latest snapshots
- References: <20100731172035.GA3617@ednor.casa.cgf.cx> <962517.70320.qm@web25505.mail.ukl.yahoo.com>
- Reply-to: 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