From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14043 invoked by alias); 28 Mar 2014 22:31:11 -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 14031 invoked by uid 89); 28 Mar 2014 22:31:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: mail-qa0-f53.google.com Received: from mail-qa0-f53.google.com (HELO mail-qa0-f53.google.com) (209.85.216.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 28 Mar 2014 22:31:09 +0000 Received: by mail-qa0-f53.google.com with SMTP id w8so5790255qac.40 for ; Fri, 28 Mar 2014 15:31:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=/hT8L+W9bWS/CHaIou8/AZKfxE9lBGD1bKzvkrCkFzU=; b=k/KOzkQ1pBeH8fhtAzLJn7rwb/uO4DOd3vr7m4TJU5LWJWPQ7cth391fE4vqD7QhU6 idv9InzZoxR8HlsDlHWLe+9IMFaCAdUZXGlhLeVdCJR/nBtUKu6pUivelhefRvibU0wd gp58t/9eTceovj3FYb68jydcQRhLn50Ajjx6h+58t2J+yYNSZCJ1fYB2RTtNduNSqZGU ToQ8J0y29IOV6+RbKHWlqCVdIEewE21evbTghAYEbKCiKp9M3Om4XY8RyzlFOuTDKdxC 7lN3rEzARQtBSVtPv2B0tHhjzPlTqSauxxEXnDkmecNWGDL4zUFQRiFpaoqKjbnEMR3T Z+LQ== X-Gm-Message-State: ALoCoQmC1WrfdtTeJxbIB51SVGwIpZ5FDItxRAFwCNZwXhMm6VIXFbkA2DSly2s6fOKq4fXYI49C X-Received: by 10.140.23.148 with SMTP id 20mr4941521qgp.89.1396045867564; Fri, 28 Mar 2014 15:31:07 -0700 (PDT) Received: from localhost ([207.112.112.168]) by mx.google.com with ESMTPSA id e4sm12599537qar.12.2014.03.28.15.31.05 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Mar 2014 15:31:06 -0700 (PDT) From: Anthony Green To: Matthias Klose Cc: libffi-discuss@sourceware.org Subject: Re: libffi 3.1-rc1 needs testing! References: <87eh2liiow.fsf@moxielogic.com> <87a9ce3ry7.fsf@moxielogic.com> <5335DDEF.9050300@ubuntu.com> <87ha6i2dk5.fsf@moxielogic.com> Date: Fri, 28 Mar 2014 22:31:00 -0000 In-Reply-To: <87ha6i2dk5.fsf@moxielogic.com> (Anthony Green's message of "Fri, 28 Mar 2014 17:55:38 -0400") Message-ID: <87d2h62bxw.fsf@moxielogic.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2014/txt/msg00050.txt.bz2 Anthony Green writes: > Ok, this suggests ABI breakage. There were recent changes in 32-bit > Linux support that may be to blame (additional ABI support). I can look > into this. I had a look at the code changes and nothing jumped out at me. Then I built a 32-bit 3.0.13 libffi on x86-64 Linux with "-m32". I did the same thing with 3.1 from github. Then I replaced the 3.0.14 libffi libraries in the build tree with the 3.1 libraries and ran 'make check'. Everything passed. So if there is any ABI breakage, it must be very subtle. Unless you have any other good ideas (and I'm hoping you do), we're going to have to reproduce this the hard way. AG > > >> >> Signal: 11 >> SourcePackage: python3.4 >> StacktraceTop: >> g_callable_info_free_closure (callable_info=0x9e8a5b0, >> closure=0xb6b43008) at girepository/girffi.c:426 >> _pygi_invoke_closure_free (data=0x9efdd50) at ../../gi/pygi-closure.c:638 >> _pygi_destroy_notify_callback_closure (cif=0x9efddbc, >> result=0xbfaec770, args=0xbfaec710, data=0x0) at >> ../../gi/pygi-closure.c:703 >> ffi_closure_SYSV_inner (closure=0xb6b43030, respp=0xbfaec77c, >> args=0xbfaec790) at ../src/x86/ffi.c:503 >> ffi_closure_SYSV () at ../src/x86/sysv.S:199