From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.7
Date: Fri, 08 Feb 2019 12:52:00 -0000 [thread overview]
Message-ID: <b07e6ba2-0ce0-4662-7a02-bda6ce3b0108@ssi-schaefer.com> (raw)
In-Reply-To: <20190208122338.GN13951@calimero.vinschen.de>
On 2/8/19 1:23 PM, Corinna Vinschen wrote:
> On Feb 8 13:21, Corinna Vinschen wrote:
>> On Feb 8 12:51, Michael Haubenwallner wrote:
>>>
>>> For now it seems like there's an inconsistency with PIDs:
>>> A first process PID 100, receives PID 101 from spawn(),
>>> but in the new process getpid() returns 102:
>>>
>>> $ ./dospawn /bin/bash -c 'echo $$'
>>> 12625
>>> waitpid: pid 12624 status 0x0
>>
>> Oh, hmm. If you call spawnve, rather than execve, a new child pid
>> is generated in spawnve, rather than just keeping the callers pid.
>>
>> However, apparently the child invents its own pid in pinfo::thisproc
>> after being spawned. But actually this should only occur for forked
>> processes aore processes started from non-Cygwin parents.
>
> Does that help, by any chance:
>
> diff --git a/winsup/cygwin/dcrt0.cc b/winsup/cygwin/dcrt0.cc
> index 78506d43de29..0b274287d9f6 100644
> --- a/winsup/cygwin/dcrt0.cc
> +++ b/winsup/cygwin/dcrt0.cc
> @@ -656,7 +656,7 @@ child_info_spawn::handle_spawn ()
> !DuplicateHandle (GetCurrentProcess (), moreinfo->myself_pinfo,
> GetCurrentProcess (), &h, 0,
> FALSE, DUPLICATE_SAME_ACCESS | DUPLICATE_CLOSE_SOURCE))
> - h = NULL;
> + h = INVALID_HANDLE_VALUE;
>
> /* Setup our write end of the process pipe. Clear the one in the structure.
> The destructor should never be called for this but, it can't hurt to be
> diff --git a/winsup/cygwin/pinfo.cc b/winsup/cygwin/pinfo.cc
> index 445bd35b224e..d10c4fc4580c 100644
> --- a/winsup/cygwin/pinfo.cc
> +++ b/winsup/cygwin/pinfo.cc
> @@ -62,6 +62,8 @@ pinfo::thisproc (HANDLE h)
> cygheap->pid = create_cygwin_pid ();
> flags |= PID_NEW;
> }
> + else if (h == INVALID_HANDLE_VALUE)
> + h = NULL;
No, because cygheap->pid still is the parent's pid here, not the new child's one.
How should the child be informed at all about the new cygpid value generated in
parent's child_info_spawn::worker() ?
/haubi/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-02-08 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:24 Corinna Vinschen
2019-02-07 16:14 ` Michael Haubenwallner
2019-02-07 18:27 ` Corinna Vinschen
2019-02-08 6:46 ` Michael Haubenwallner
2019-02-08 11:32 ` Corinna Vinschen
2019-02-08 11:51 ` Michael Haubenwallner
2019-02-08 12:21 ` Corinna Vinschen
2019-02-08 12:23 ` Corinna Vinschen
2019-02-08 12:52 ` Michael Haubenwallner [this message]
2019-02-08 13:06 ` Corinna Vinschen
2019-02-08 13:28 ` Corinna Vinschen
2019-02-08 14:43 ` Michael Haubenwallner
2019-02-08 14:49 ` Corinna Vinschen
2019-02-08 16:18 ` Michael Haubenwallner
2019-02-08 16:50 ` Corinna Vinschen
2019-02-08 16:35 ` Michael Haubenwallner
2019-02-08 16:58 ` Corinna Vinschen
2019-02-08 17:00 ` Corinna Vinschen
2019-02-11 11:50 ` Michael Haubenwallner
2019-02-11 13:33 ` Corinna Vinschen
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=b07e6ba2-0ce0-4662-7a02-bda6ce3b0108@ssi-schaefer.com \
--to=michael.haubenwallner@ssi-schaefer.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).