is fork() supported?

[Jay K]

On my point, sorry:


  1.  Sorry, I assumed mail from DJ was about djgpp, and that context was lacking in libffi. My mistake.
  2.  Either way, I was referring to the work that came after "trampfd", with the static trampolines that get mmaped repeatedly.
  3.  So libffi no longer has read/write/execute memory, or turns read/write into execute, correct?
  4.  So the implied assertion or question then, does that work very much sweep away "all such problems", or some remain?

 - Jay

________________________________
From: Libffi-discuss <libffi-discuss-bounces+jay.krell=cornell.edu@sourceware.org> on behalf of DJ Delorie via Libffi-discuss <libffi-discuss@sourceware.org>
Sent: Tuesday, August 24, 2021 6:15 PM
To: libffi-discuss@sourceware.org <libffi-discuss@sourceware.org>
Subject: Re: is fork() supported?

Florian Weimer via Libffi-discuss <libffi-discuss@sourceware.org>
writes:
>> The bug that will never die.
> Well, there are two ways to fix it:

The thread ended without resolution...  we've (RH) got a bug report
against it, and I need to know if I can tell them "don't do that" or if
I'm obligated to pursue some fix.

So my question isn't CAN we fix it, it's MUST we fix it...  I.e. is this
a supported feature, or something that 'happened to work' so got abused?