From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69667 invoked by alias); 18 Aug 2017 13:09:06 -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 69018 invoked by uid 89); 18 Aug 2017 13:09:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=python2, sufficiently, observation, joachim X-HELO: mail-io0-f175.google.com Received: from mail-io0-f175.google.com (HELO mail-io0-f175.google.com) (209.85.223.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 18 Aug 2017 13:09:03 +0000 Received: by mail-io0-f175.google.com with SMTP id g35so32697115ioi.3 for ; Fri, 18 Aug 2017 06:09:03 -0700 (PDT) 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=cRhgX8HuqwcXIIg9qjE1a6E7825dzVFOfY10Ijp4YHU=; b=RUmpGvjAKFMm42tTwzegirLJNhq9XblTGO/qwjiAOjWk0wL/enDwYzPtsSE46lGIFv UViFITWNQIBNDw7+3Ib3a1o4rGDubgYXIMYaySQ35+9wx2WKZM/jsKUoftLVIHFo34oD RDa+L5IOD8b7WeidzvypNQ6v8oFOYIzapq793MNe9VSHLGO1hhrC0GYpUtzZEaScABpA eF456ESsB0XtWoTnP6MRSvikvIAS9KMNrKVXkN0IsFIpMxwYNduZgEaPYbhwjg8Go0ma SOUW8+7HcVJmAFurioCzg/lErBilVgPryt26YDWJhUqxtbxhf2yZ2K808BJ+hxbxD1Zl 097Q== X-Gm-Message-State: AHYfb5joihcPQ3wxmc7nJ1iWEqz+tA4GlP1F+aU+ASpOYgHI7tAyy7lL z0dl8XRW4zdABTuw X-Received: by 10.107.53.40 with SMTP id c40mr8479781ioa.289.1503061741435; Fri, 18 Aug 2017 06:09:01 -0700 (PDT) Received: from [192.168.0.6] (d4-50-42-50.try.wideopenwest.com. [50.4.50.42]) by smtp.gmail.com with ESMTPSA id o202sm655229itc.37.2017.08.18.06.09.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Aug 2017 06:09:00 -0700 (PDT) Subject: Re: gcc segfaults compiling python extensions To: cygwin@cygwin.com References: From: cyg Simple Message-ID: Date: Fri, 18 Aug 2017 13:09:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00167.txt.bz2 On 8/18/2017 1:21 AM, Joachim Metz wrote: > Hello CygWin maintainers, > > I want to report an observation, which might help address a bug. > > This issue has been reported in the past in: > https://cygwin.com/ml/cygwin/2014-10/msg00502.html > > I recently ran into the same issue: > > On AppVeyor [https://ci.appveyor.com/] running Windows Server 2012 R2 > With the latest available cygwin 32-bit > [https://github.com/libyal/libfwnt/blob/master/appveyor.yml#L39] > > building a Python module for CygWin python (no Windows Python) causes > gcc to SIGSEGV (11) > > gcc -fno-strict-aliasing -ggdb -O2 -pipe > -Wimplicit-function-declaration > -fdebug-prefix-map=/usr/src/ports/python2/python2-2.7.13-1.i686/build=/usr/src/debug/python2-2.7.13-1 > -fdebug-prefix-map=/usr/src/ports/python2/python2-2.7.13-1.i686/src/Python-2.7.13=/usr/src/debug/python2-2.7.13-1 > -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DHAVE_CONFIG_H= > -DLOCALEDIR="/usr/share/locale" -Iinclude -Icommon -Ilibcerror > -Ilibcthreads -Ilibcdata -Ilibcnotify -Ilibfwnt > -I/usr/include/python2.7 -c libcerror/libcerror_error.c -o > build/temp.cygwin-2.8.2-i686-2.7/libcerror/libcerror_error.o > error: command 'gcc' terminated by signal 11 > Running: 'setup.py build' failed > 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. > Also see: https://ci.appveyor.com/project/joachimmetz/libfwnt/build/79/job/l1gqocdqoafax0k7 > > > As per: https://cygwin.com/ml/cygwin/2014-10/msg00552.html I switched > to Windows Server 2016 and this indeed does not show the same issue. > 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. > I've been tracking this in: https://github.com/libyal/libyal/issues/34 > > Hope to have sufficiently informed you. > > Let me know if you need additional information. 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. -- 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