public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: nathan@tootallnate.net, bobbyholley@gmail.com
Cc: twall@users.sf.net, libffi-discuss@sourceware.org, green@moxielogic.com
Subject: Re: Bus Error while trying to run the ffi_closure example in the documentation...
Date: Mon, 09 Jan 2012 03:06:00 -0000	[thread overview]
Message-ID: <555253936.13763429.1326078376487.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

Hey guys.. I'm currently enjoying Yosmite park.  I'll catch up on all of the email when I return next week.

Thanks,

AG


-----Original Message-----
From: Bobby Holley [bobbyholley@gmail.com]
Received: Sunday, 08 Jan 2012, 6:37pm
To: Nathan Rajlich [nathan@tootallnate.net]
CC: Timothy Wall [twall@users.sf.net]; libffi-discuss [libffi-discuss@sourceware.org]; green@moxielogic.com
Subject: Re: Bus Error while trying to run the ffi_closure example in the documentation...


> Omg Bobby you're a life saver! That patch did the trick. Thanks all
> for all the help! Consider my case solved :)

\o/

It would be nice to make sure it's solved for everyone else too ;-).
Anthony, is this patch on the radar for libffi?

Cheers,
-bholley

             reply	other threads:[~2012-01-09  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  3:06 Anthony Green [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=555253936.13763429.1326078376487.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com \
    --to=green@redhat.com \
    --cc=bobbyholley@gmail.com \
    --cc=green@moxielogic.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=nathan@tootallnate.net \
    --cc=twall@users.sf.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).