From: Timothy Wall <twall@users.sf.net>
To: Nathan Rajlich <nathan@tootallnate.net>
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: Bus Error while trying to run the ffi_closure example in the documentation...
Date: Sat, 07 Jan 2012 20:53:00 -0000 [thread overview]
Message-ID: <99F0629B-EA20-4AFD-B9F2-375A59E96658@users.sf.net> (raw)
In-Reply-To: <CAN5MXod3ncAc7n9Ju-0oC-5Kqhsgy2yz+1732wAkFzu7xhrBCw@mail.gmail.com>
I'm using ffi_closure on OSX (not lion, though) amd64 target and it performs as expected for me.
Have you run the testsuite? there are ffi_closure tests in that.
On Jan 7, 2012, at 3:28 PM, Nathan Rajlich wrote:
> Ok so as a little update, the test program I linked to above work on
> my Windows XP VM and Ubuntu VMs, so it looks like this might be
> something with either the Darwin 64-bit support, or something with my
> configuration. If somebody else has an OS X setup and could compile
> the example above it would be really helpful. Thanks in advance!
>
> On Sat, Jan 7, 2012 at 12:14 PM, Nathan Rajlich <nathan@tootallnate.net> wrote:
>> Awww nobody? Well for easier reference, here's the source code used in
>> question: https://gist.github.com/1575877 . It's straight from the
>> libffi docs. Hopefully with the source here somebody else can try
>> compiling and letting me know the result. Thanks!
>>
>> On Fri, Jan 6, 2012 at 12:17 PM, Nathan Rajlich <nathan@tootallnate.net> wrote:
>>> Hey all,
>>>
>>> So I'm trying to run the ffi_closure example from the libffi
>>> documentation (the one that wraps fputs() ). When trying to run the
>>> program, I get a "Bus Error: 10" and the program crashes.
>>>
>>> This is on OS X 64-bit (Lion). Put through gdb, this is what I get:
>>>
>>> ∞ ~/node-ffi/deps (gyp) $ gdb --args ./out/Debug/test
>>> GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011)
>>> Copyright 2004 Free Software Foundation, Inc.
>>> GDB is free software, covered by the GNU General Public License, and you are
>>> welcome to change it and/or distribute copies of it under certain conditions.
>>> Type "show copying" to see the conditions.
>>> There is absolutely no warranty for GDB. Type "show warranty" for details.
>>> This GDB was configured as "x86_64-apple-darwin"...Reading symbols for
>>> shared libraries ... done
>>>
>>> (gdb) run
>>> Starting program: /Users/nrajlich/node-ffi/deps/out/Debug/test
>>> Reading symbols for shared libraries ++......................... done
>>>
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: KERN_PROTECTION_FAILURE at address: 0x0000000100100a20
>>> 0x0000000100100a20 in ?? ()
>>> (gdb) bt
>>> #0 0x0000000100100a20 in ?? ()
>>> #1 0x0000000100001424 in start ()
>>>
>>>
>>> Thanks for looking, any thoughts would be appreciated! Cheers!
next prev parent reply other threads:[~2012-01-07 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 20:18 Nathan Rajlich
2012-01-07 20:14 ` Nathan Rajlich
2012-01-07 20:29 ` Nathan Rajlich
2012-01-07 20:53 ` Timothy Wall [this message]
2012-01-08 6:28 ` Bobby Holley
2012-01-08 8:58 ` Nathan Rajlich
2012-01-09 2:37 ` Bobby Holley
2012-01-23 18:51 ` Anthony Green
2012-01-09 3:06 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=99F0629B-EA20-4AFD-B9F2-375A59E96658@users.sf.net \
--to=twall@users.sf.net \
--cc=libffi-discuss@sourceware.org \
--cc=nathan@tootallnate.net \
/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).