From: Andrew Haley <aph@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: libffi & fork
Date: Wed, 25 Apr 2012 09:11:00 -0000 [thread overview]
Message-ID: <4F97BF9E.6070103@redhat.com> (raw)
In-Reply-To: <CAP+vr+MMKXaea2oGYH8srmMstyBVmQQYmziX=wVOgoB8g3Ofaw@mail.gmail.com>
On 04/24/2012 08:40 PM, Gaash Hazan wrote:
> I am new to libffi, so forgive me for my ignorance.
>
> I have a python crash involving ctypes and functions callbacks (read
> closures) and fork. The crash happens when process is forked, some
> callbacks are modified and a function callback is made. I suspect that
> the problem could be related to libffi closures and fork.
There is, as far as I can see, only one way to remedy this: allow
python to map anonymous memory with both write and execute permission.
Then it should work fine.
Andrew.
next prev parent reply other threads:[~2012-04-25 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP+vr+PX9gw7Ot6Zc7AN8Gks9P+WHVQg8bX5S7YRnTRyRBHp7A@mail.gmail.com>
2012-04-24 19:41 ` Gaash Hazan
2012-04-25 9:11 ` Andrew Haley [this message]
2012-04-25 17:33 ` Gaash Hazan
2012-04-26 10:00 ` Andrew Haley
2012-04-29 15:34 ` Gaash Hazan
2012-04-29 17:58 ` Anthony Green
2012-04-30 8:32 ` Andrew Haley
2012-04-30 19:16 ` Anthony Green
2012-05-01 7:56 ` Andrew Haley
2012-05-02 20:23 ` Anthony Green
2012-05-04 9:00 ` Andrew Haley
2012-05-05 13: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=4F97BF9E.6070103@redhat.com \
--to=aph@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).