From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101407 invoked by alias); 23 Aug 2017 19:38:31 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 101374 invoked by uid 89); 23 Aug 2017 19:38:30 -0000 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 Received: from mail-qt0-f174.google.com (HELO mail-qt0-f174.google.com) (209.85.216.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 23 Aug 2017 19:38:29 +0000 Received: by mail-qt0-f174.google.com with SMTP id x36so5883331qtx.2 for ; Wed, 23 Aug 2017 12:38:29 -0700 (PDT) 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 Received: by 10.237.41.98 with HTTP; Wed, 23 Aug 2017 12:38:27 -0700 (PDT) From: Joachim Metz Date: Wed, 23 Aug 2017 19:38:00 -0000 Message-ID: Subject: Re: gcc segfaults compiling python extensions To: cyg Simple , cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2017-08/txt/msg00215.txt.bz2 > 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