From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21018 invoked by alias); 3 Jun 2016 16:49:48 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 21003 invoked by uid 89); 3 Jun 2016 16:49:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_00,KAM_COUK,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=HTo:U*libffi-discuss, H*Ad:D*co.uk, our X-HELO: ducie-dc1.codethink.co.uk Received: from ducie-dc1.codethink.co.uk (HELO ducie-dc1.codethink.co.uk) (185.25.241.215) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 03 Jun 2016 16:49:46 +0000 Received: from localhost (localhost [127.0.0.1]) by ducie-dc1.codethink.co.uk (Postfix) with ESMTP id 66A67462AD4 for ; Fri, 3 Jun 2016 17:49:43 +0100 (BST) Received: from ducie-dc1.codethink.co.uk ([127.0.0.1]) by localhost (ducie-dc1.codethink.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krXKt0qZGvdO for ; Fri, 3 Jun 2016 17:49:41 +0100 (BST) Received: from [10.24.1.182] (82-70-136-246.dsl.in-addr.zen.co.uk [82.70.136.246]) by ducie-dc1.codethink.co.uk (Postfix) with ESMTPSA id 9C9344609CA for ; Fri, 3 Jun 2016 17:49:41 +0100 (BST) To: libffi-discuss@sourceware.org From: Pedro Alvarez Subject: Python core-dumps when compiled with GCC-6 Message-ID: <5751B525.2070707@codethink.co.uk> Date: Fri, 03 Jun 2016 16:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2016/txt/msg00026.txt.bz2 Hi! We are currently trying to upgrade our systems to GCC 6.1.0 but I'm facing a problem with python (compiled with libffi enabled). Python core-dump's saying that is because libffi.so, I wonder if you now anything about it, or if this is just a problem of libffi not being ready for GCC 6. Removing libffi.so from the system "fixes" the problem, but is not a real fix for us. Also, I've tried to upgrade to latest version of libffi (master from git repo) but it didn't work either. Any hints? Thanks for helping, Pedro