Re: gcc segfaults compiling python extensions

[cyg Simple <cygsimple@gmail.com>]

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