public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Hogan, Christopher" <christopher.hogan@intel.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: x86_64 build on Mac OS X
Date: Mon, 05 Oct 2015 20:09:00 -0000	[thread overview]
Message-ID: <18A68EC651142A408A0A6AFDE7D1FC895C475F@ORSMSX103.amr.corp.intel.com> (raw)

Hello,

I'm trying to build libffi 3.2.1 with the Intel compiler v15 on OS X Yosemi= te 10.10.  It appears to build successfully, but when I build a python bina= ry (cpython) using my built libffi and run the regression tests I get 12 se= gmentation faults, all of which are caused by `ffi_prep_closure_loc` in lib= ffi.6.dylib which gets called from _ctypes_alloc_callback in _ctypes.so.

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000000282ffc0

VM Regions Near 0x282ffc0:
-->
    __TEXT                 0000000100000000-0000000100273000 [ 2508K] r-x/r=
wx SM=3DCOW  /nfs/*

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libffi.6.dylib                      0x000000010788636d ffi_prep_closure=
_loc + 29
1   _ctypes.so                          0x000000010280cc98 _ctypes_alloc_ca=
llback + 424
2   _ctypes.so                          0x000000010280593b PyCFuncPtr_new +=
 427

Do you support 64 bit builds on OS X running a 2.8 GHz Intel Core i5?

Chris Hogan
Scripting Tools Engineer
Scripting, Analyzers and Tools
Intel Corporation

                 reply	other threads:[~2015-10-05 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=18A68EC651142A408A0A6AFDE7D1FC895C475F@ORSMSX103.amr.corp.intel.com \
    --to=christopher.hogan@intel.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).