From: DJ Delorie <dj@redhat.com>
To: Anthony Green <green@redhat.com>
Cc: libffi-discuss@sourceware.org, fweimer@redhat.com
Subject: Re: segfault in ffi_data_to_code_pointer
Date: Thu, 04 Jul 2019 00:19:00 -0000 [thread overview]
Message-ID: <xnd0iqslb7.fsf@greed.delorie.com> (raw)
In-Reply-To: <878ste90dy.fsf@laptop.atgreen.org> (message from Anthony Green on Wed, 03 Jul 2019 19:14:17 -0400)
Anthony Green <green@redhat.com> writes:
> Thanks. This looks right to me.
By "right" do you mean "wrong" ?
> Perhaps they wrote this before ffi_closure_alloc() existed? I don't
> remember when every bit was introduced... Looks like you need to
> follow up with the ruby people.
So... no need/desire/reason to change anything in libffi then? ;-)
next prev parent reply other threads:[~2019-07-04 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 20:55 DJ Delorie
2019-06-30 11:46 ` Anthony Green
2019-07-02 23:47 ` DJ Delorie
2019-07-03 22:28 ` DJ Delorie
2019-07-03 22:47 ` Anthony Green
2019-07-03 22:54 ` DJ Delorie
2019-07-03 23:14 ` Anthony Green
2019-07-04 0:19 ` DJ Delorie [this message]
2019-07-04 12:35 ` Florian Weimer
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=xnd0iqslb7.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=green@redhat.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).