From: Anthony Green <green@moxielogic.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi 3.1-rc1 needs testing!
Date: Fri, 28 Mar 2014 21:56:00 -0000 [thread overview]
Message-ID: <87ha6i2dk5.fsf@moxielogic.com> (raw)
In-Reply-To: <5335DDEF.9050300@ubuntu.com> (Matthias Klose's message of "Fri, 28 Mar 2014 21:39:11 +0100")
Matthias Klose <doko@ubuntu.com> writes:
> Am 25.03.2014 22:10, schrieb Anthony Green:
>> I am still hoping to get a release out before April, but I'll need
>> plenty of help with the testing...
>
> the good news is that the testsuite passes on every Debian and Ubuntu
> architecture without test failures. The bad news is that it is broken
> on x86 (not x86_64).
>
> running the python, ruby-ffi, cffi testsuites against the newly built
> libffi, it breaks with segfaults.
>
> A small reproducer is (taken from https://launchpad.net/bugs/1298824):
>
> sudo apt-get install python3-gi gir1.2-gtk-3.0 xvfb
> xvfb-run python3 -c 'from gi.repository import GLib, Gtk;
> GLib.timeout_add_seconds(1, Gtk.main_quit, None); Gtk.main()'
>
> It is pointed out that rebuilding the depending packages fixes the
> segfaults.
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.
Thanks for the pointer!
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
next prev parent reply other threads:[~2014-03-28 21:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 23:49 libffi 3.0.14-rc0 " Anthony Green
2014-03-01 23:56 ` Anthony Green
2014-03-03 12:44 ` Dominik Vogt
2014-03-03 19:17 ` David Fang
2014-03-04 7:29 ` Will Newton
2014-03-05 0:31 ` Alan Hourihane
2014-03-04 22:14 ` Matthias Klose
2014-03-25 21:11 ` libffi 3.1-rc1 " Anthony Green
2014-03-27 12:23 ` Dominik Vogt
2014-03-27 12:25 ` Dominik Vogt
2014-03-27 12:31 ` Dominik Vogt
2014-03-27 12:40 ` Samuli Suominen
2014-03-27 12:45 ` Samuli Suominen
2014-03-27 12:55 ` Samuli Suominen
2014-03-28 15:43 ` Anthony Green
2014-03-28 15:05 ` James Greenhalgh
2014-03-28 17:33 ` Anthony Green
2014-04-24 12:47 ` Marcus Shawcroft
2014-03-28 20:37 ` Andreas Tobler
2014-03-28 20:39 ` Matthias Klose
2014-03-28 21:56 ` Anthony Green [this message]
2014-03-28 22:31 ` Anthony Green
2014-03-29 14:25 ` ABI breakage (Was: libffi 3.1-rc1 needs testing!) Anthony Green
2014-05-30 12:21 ` Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ha6i2dk5.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=doko@ubuntu.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).