From: Nathan Rajlich <nathan@tootallnate.net>
To: libffi-discuss <libffi-discuss@sourceware.org>
Cc: Andrew Haley <aph@redhat.com>, Reini Urban <rurban@x-ray.at>
Subject: Re: "closures" not working on OS X 10.8 (Mountain Lion)?
Date: Wed, 15 Aug 2012 05:23:00 -0000 [thread overview]
Message-ID: <CAN5MXoe6r4+SppJu-LB3nxqVbCb7a1QvK5Q13d0wkZ2Cd5BSrg@mail.gmail.com> (raw)
In-Reply-To: <CAHiT=DH53G_ZQouNyuwogmMS8CieUWydd8Tf0WgnLks-Xs+BzQ@mail.gmail.com>
Bobby, I believe that that patch has indeed been merged upstream in
https://github.com/atgreen/libffi/commit/236c9391321f83ad40daf03f40c35c9ebc1da6b3.
So I guess it's not that.
Reini, that sounded like a good idea to me but it doesn't seem to
change anything for me. This is what I did:
$ cd libffi # still the v3.0.11 tag
$ CFLAGS="-Xlinker -no_pie" CXXFLAGS="-Xlinker -no_pie"
LDFLAGS="-no_pie" ./configure --enable-static --disable-shared
--disable-builddir --with-pic
$ CFLAGS="-Xlinker -no_pie" CXXFLAGS="-Xlinker -no_pie" LDFLAGS="-no_pie" make
$ gcc -o closure-test closure.c .libs/libffi.a -Iinclude -Xlinker -no_pie
$ ./closure-test
Bus error: 10
Andrew, well shucks :)
Anybody else have any ideas?
On Tue, Aug 14, 2012 at 8:18 AM, Reini Urban <rurban@x-ray.at> wrote:
> On Tue, Aug 14, 2012 at 9:40 AM, Andrew Haley <aph@redhat.com> wrote:
>> On 08/13/2012 07:28 PM, Nathan Rajlich wrote:
>>> It seems to me that closures are no longer working on OS X v10.8
>>> (a.k.a. Mountain Lion). I first noticed this when the node-ffi test
>>> suite started failing with a "Bus Error", so just now I ran a simple
>>> closure example from the internet and encounter the same error when I
>>> try to run that. Note that this is using the libffi v3.0.11 tag. My
>>> test case and shell session are outlined in this gist here:
>>> https://gist.github.com/3342783.
>>>
>>> I don't personally know what's going on here, but am hoping somebody
>>> on this list will. I can provide any more additional information
>>> necessary. Cheers and thanks in advance!
>>
>> This is probably because of heap execute protection. Unfortunately I
>> don't know how it works on OS X: you need an Apple export.
>
> --no_pie is needed.
>
> See also http://code.google.com/p/address-sanitizer/issues/detail?id=29
> how to disable ASLR with various MacOSX versions:
> e.g. export DYLD_NO_PIE=1 on 10.6
> link with --no_pie since 10.7
> --
> Reini Urban
> http://cpanel.net/ http://www.perl-compiler.org/
next prev parent reply other threads:[~2012-08-15 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 18:28 Nathan Rajlich
2012-08-14 14:40 ` Andrew Haley
2012-08-14 15:19 ` Reini Urban
2012-08-15 5:23 ` Nathan Rajlich [this message]
2012-09-13 0:51 ` Nathan Rajlich
2012-09-16 21:10 ` Nathan Rajlich
2012-10-30 18:19 ` Anthony Green
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=CAN5MXoe6r4+SppJu-LB3nxqVbCb7a1QvK5Q13d0wkZ2Cd5BSrg@mail.gmail.com \
--to=nathan@tootallnate.net \
--cc=aph@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=rurban@x-ray.at \
/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).