public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: gs-cygwin.com@gluelogic.com
To: Dan Shelton <dan.f.shelton@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Native posix_spawn() in Cygwin?
Date: Tue, 27 Feb 2024 01:34:45 -0500	[thread overview]
Message-ID: <Zd2ChRq46MUMv0rU@xps13> (raw)
In-Reply-To: <CAAvCNcDeYwhpq4Q9ftRgq3oErZNiS=x7DaLr-Lt6gAzG-npGfA@mail.gmail.com>

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?

Cheers, Glenn

  reply	other threads:[~2024-02-27  6:34 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 [this message]
2024-03-04  3:27       ` Dan Shelton
2024-03-04  6:45         ` Mark Geisert
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=Zd2ChRq46MUMv0rU@xps13 \
    --to=gs-cygwin.com@gluelogic.com \
    --cc=cygwin@cygwin.com \
    --cc=dan.f.shelton@gmail.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).