Re: libffi 3.1-rc1 needs testing!

[Anthony Green <green@moxielogic.com>]

Anthony Green <green@moxielogic.com> 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