This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libffi & fork

From: Andrew Haley <aph at redhat dot com>
To: libffi-discuss at sourceware dot org
Date: Wed, 25 Apr 2012 10:10:54 +0100
Subject: Re: libffi & fork
References: <CAP+vr+PX9gw7Ot6Zc7AN8Gks9P+WHVQg8bX5S7YRnTRyRBHp7A@mail.gmail.com> <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.

Follow-Ups:
- Re: libffi & fork
  - From: Gaash Hazan

References:
- libffi & fork
  - From: Gaash Hazan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]