From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Native posix_spawn() in Cygwin?
Date: Sun, 3 Mar 2024 22:45:14 -0800 [thread overview]
Message-ID: <da003a14-a7ea-46d8-8ded-0f4e49290704@maxrnd.com> (raw)
In-Reply-To: <CAAvCNcBTRkJuD52dZsPePAG_yK_cBc=Ps4QPeG1BBXdZp5OYdg@mail.gmail.com>
On 3/3/2024 7:27 PM, Dan Shelton via Cygwin wrote:
> On Tue, 27 Feb 2024 at 07:34, <gs-cygwin.com@gluelogic.com> wrote:
>>
>> On Tue, Feb 27, 2024 at 06:54:42AM +0100, Dan Shelton via Cygwin wrote:
>>> On Tue, 27 Feb 2024 at 06:47, Brian Inglis via Cygwin <cygwin@cygwin.com> wrote:
>>>>
>>>> On 2024-02-26 20:23, Dan Shelton via Cygwin wrote:
>>>>> Does Cygwin implement a native, i.e. without form(),exec(), implementation of posix_spawn()?
>>>>
>>>> Check the API compatibility docs online:
>>>>
>>>> https://cygwin.com/cygwin-api/compatibility.html#std-susv4
>>>>
>>>> or optional locally installed package cygwin-doc:
>>>>
>>>> /usr/share/doc/cygwin-doc/html/cygwin-api/compatibility.html#std-susv4
>>>
>>> That document does not answer my question.
>>>
>>> I know posix_spawn() is there. But the question is: Does it use just
>>> Cygwin fork(),exec(), or the native Win32 spawn() api?
>>>
>>> Dan
>>> --
>>> Dan Shelton - Cluster Specialist Win/Lin/Bsd
>>
>> If you were going to make a small effort to answer the question
>> yourself, you could use strace, you could step through a debugger, or
>> you could check the source code. Have you tried any of these? What did
>> you find? If you are unable to take any of those steps, why does
>> posix_spawn() matter to you?
>
> strace does not help, as I need the Win32 calls BELOW posix_spawn(),
> to see the implementation details.
Check the source code, then. It's at:
https://cygwin.com/cgit/newlib-cygwin/tree/winsup/cygwin/fork.cc
Look at line 587; there's the static function dofork(). Look at the
thirty or so lines above that; there's both fork() and
__posix_spawn_fork() calling dofork(). So both those user-level
functions call into the exact same internals. (BTW __posix_spawn_fork()
is called from posix_spawn(); the latter is in newlib and not Cygwin.)
You can even see the reason it's done this way by reading the comment.
..mark
next prev parent reply other threads:[~2024-03-04 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 3:23 Dan Shelton
2024-02-27 5:47 ` Brian Inglis
2024-02-27 5:54 ` Dan Shelton
2024-02-27 6:34 ` gs-cygwin.com
2024-03-04 3:27 ` Dan Shelton
2024-03-04 6:45 ` Mark Geisert [this message]
2024-03-05 22:42 ` Dan Shelton
2024-03-06 0:08 ` Mark Geisert
2024-03-06 14:23 ` Roland Mainz
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=da003a14-a7ea-46d8-8ded-0f4e49290704@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/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).