From: Jay K <jayk123@hotmail.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
DJ Delorie <dj@redhat.com>
Subject: Re: is fork() supported?
Date: Tue, 24 Aug 2021 18:27:39 +0000 [thread overview]
Message-ID: <MWHPR1401MB1951130BC2E08E7A284F1238E6C59@MWHPR1401MB1951.namprd14.prod.outlook.com> (raw)
In-Reply-To: <xnfsuy4sku.fsf@greed.delorie.com>
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?
next prev parent reply other threads:[~2021-08-24 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 20:00 DJ Delorie
2021-08-05 8:17 ` Andrew Haley
2021-08-05 8:27 ` Florian Weimer
2021-08-24 18:15 ` DJ Delorie
2021-08-24 18:27 ` Jay K [this message]
2021-08-24 18:45 ` DJ Delorie
2021-08-24 21:12 ` Kaz Kylheku (libffi)
2021-08-24 21:58 ` Jay K
2021-08-25 9:27 ` Andrew Haley
2021-08-25 15:58 ` Jay K
2021-08-25 16:59 ` Kaz Kylheku (libffi)
2021-08-25 21:17 ` Andrew Haley
2021-08-05 18:13 ` DJ Delorie
2021-08-05 21:21 ` Jay K
2021-08-06 8:32 ` Andrew Haley
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=MWHPR1401MB1951130BC2E08E7A284F1238E6C59@MWHPR1401MB1951.namprd14.prod.outlook.com \
--to=jayk123@hotmail.com \
--cc=dj@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).