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:mime-version:from:date:message-id:subject:to :content-type; q=dns; s=default; b=d4TOnX/78zsZTmFNlk+5pKmLGhhoi tjQTNU4IT6xvCpvSBEcQl6CZbp4uXMeV57E7urX0BypuSc0gza5Y/SyE0tGgi+1J d5TR7CjtuOU67NYjbXP3UIzdTTrCVH9BE7Zb9IMBSOTNdXc2doY6KUu2I/UlvBq8 75Orp0k473mAUk= 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:mime-version:from:date:message-id:subject:to :content-type; s=default; bh=xmt1VAxBPDfYG2c4ZrV9q0vy86A=; b=mt0 NIdcsnHm53ayJO1GPQF5vquajxnYGMvPppAs54cSSSpzeW0b0oCpobDrdkvVCapN Rg7SaF1uKc/YKsEpht4FsYZwnyMk5GBpwnZL5kar3aa8m9gybMZ9fO5VYSyif3Sp D75+KOE5FYhpyRfPz7rJSlh5NS3CHrEIF5loU0TU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy= X-HELO: mail-qt0-f174.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wRyGz6CNmKVwGyndoCZqCQ7iB+0ZgCkXelaCOHh2noU=; b=DPLp+tin9uxo1O0pRsPC/FZDO6Z3cisoKZTaZt7cELsh6/WUmD3ZWxmDML8Ibrp4ul AEqNMLHjKhl9YWevdxlRMwR+XwnxBP4sHAQwPz0Rqt/a8G5nPQnviFNE8eqJ1csIbWqT fKGkn8bnvvozLTcxYIE0EZeIEQb12HGkVDNI398CeSwHP+SR4ZCLcvzErblBAapuvSdv BmONag01vpu3QUAeywj2/ZwZdGZeWBbrMKx5WUu5Unez9v1b4nrgs84l6P88gbzV0gQb Oyv8MJTXEHM0r6fAsa5X4G7mwCgqZVWEzhbgo8j6JQkT7FrXXdX5kPvsW6WgSbn30Vk6 4xIw== X-Gm-Message-State: AHYfb5jDjpEbFk4xmHmjOBCvweYlBmcaPI2tor3aUrUuWMcXzwuzzOqD 3yGoeG58/nOV8xoLjZjkLjpfHuOb0A== X-Received: by 10.200.8.3 with SMTP id u3mr5749762qth.288.1503517107894; Wed, 23 Aug 2017 12:38:27 -0700 (PDT) MIME-Version: 1.0 From: Joachim Metz Date: Wed, 23 Aug 2017 21:38:27 +0200 Message-ID: Subject: Re: gcc segfaults compiling python extensions To: cyg Simple , cygwin AT cygwin DOT com Content-Type: text/plain; charset="UTF-8" > 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. -- 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