X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=jk6E5gaaN+JdIJ6Y
	qWOvj2rKclvONLf4jpeLK5jlas9xSrKabjkiB1Ycee3RLlXbJbX+be0QEgbWMv5W
	LoLxne4hEMxcpTCyDClCTdV8oteK0MjXO7wo0ibcIRKx0SrE04osZYGc23RsdzdH
	ulJWyeXWAoE5FOVm8wYCndsD59Y=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=9mpQ422b2e897nbbDy4NiO
	t8tKo=; b=WFAPI7s/UBIM0kmarhLX+aVvRLx1HwtfB+cXRsKOA3WFCd5Ojjt2hS
	k04NfYXYDGza+/NQEIb+qqoxHkw3vHTHu8ecxPaEo5d5G+Ff8U9oPOp2IzEe3WO2
	LDdLzGNqe5nbWP0kZG/6xNN6LPuV9sh4y7V8j/XnTPZ5UsnuTWh9k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=HContent-Transfer-Encoding:8bit
X-HELO:	mail-io0-f180.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=n0K+Vw6rJowfXy/68z7ARqQk2mjutL20zTPLnb2JmYU=; b=kHcLvxsJN1mU2K/z/iM3lR7OrMdB4yERtlPNdhdq9lt6peevY+6jrju1r3xbfvoWAV I4+ApIPUJllMHcgGLB/8pphT685ArtkfR/Yg2WML94COmFDtzM6TZl3nsRKXAENe/+BC P5C5qG8tk2lzkSqD3NZTAj+qtdUJbcGuMhTGTNB+TEnTvjR/LlpLMZ3NMzwMB/yzwj0d sHIinZzeExNLoim1TYvIvQMXEX4BmIcB1yKQG01MWYuF3PmNTWTlS6m4Y9vu75mz90qi rwvl4iGoXH0pQE5n4AcZxfZgdc4RdpU5sHS7ht7prNDaHVIRzLx5XowTnbh7M7LRst59 lLWQ==
X-Gm-Message-State:	AHYfb5hM6r0bKf2vGP77/7h4jJ0NJ2BqejblRppP8N8OwonkneNBlZ1w OiyDURInYOFxlEJ9
X-Received:	by 10.107.9.210 with SMTP id 79mr2973454ioj.313.1503517935243; Wed, 23 Aug 2017 12:52:15 -0700 (PDT)
Subject:	Re: gcc segfaults compiling python extensions
To:	cygwin AT cygwin DOT com
References:	<CAPq-Lw3rgo+B5HAOW6uypLEaRGAAW7xQGFmCt=Uqrok1jpsNNw AT mail DOT gmail DOT com>
From:	cyg Simple <cygsimple AT gmail DOT com>
Message-ID:	<42fd317d-e9b9-7192-a914-666b888bfb85@gmail.com>
Date:	Wed, 23 Aug 2017 15:52:16 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version:	1.0
In-Reply-To:	<CAPq-Lw3rgo+B5HAOW6uypLEaRGAAW7xQGFmCt=Uqrok1jpsNNw@mail.gmail.com>
X-IsSubscribed:	yes

Please do not add me to the addresses directly.  I get the mail from the
list.  Note, if you're not subscribed you should be, I've removed you
from the address lists as well.

On 8/23/2017 3:38 PM, Joachim Metz wrote:
>> Was there a stackdump file you could have attached?  What happens if you
>> remove the -O3 and -O2 for that matter. I find it interesting that
>> you're using a 32bit Cygwin on a server that only executes on a 64bit
>> CPU.  Does this happen with 64bit Cygwin?  No, then use it instead.
> 
> So this does not happen on 64-bit Cygwin. I use both this is part of
> CI testing I want to have the code compile on both, or skip the test
> scenario.
> 
>> So some anomaly in Windows itself was resolved.  Should we really worry
>> about such an issue in Cygwin?  Only if Cygwin is using some API that is
>> only available in Windows Server 2016 is my POV.
> 
> Recent similar failures have me think the issue is still there even on
> newer versions of Windows.
> https://ci.appveyor.com/project/joachimmetz/libfwsi/build/job/ljhihmejb6xfyaqe
> 
>> You could try debugging the failures.  Follow the gcc issue with an
>> strace of the processes.  Attach the stackdump file if one was created, etc.
> 
> Seeing the issue seems to be still there, when time permits, I'll see
> what information I can collect regarding this issue and update this
> thread.
> 

Until you provide more information there is nothing we can do to help you.

-- 
cyg Simple

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

- Raw text -