From: Warren Young <warren@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Design mixed 32 and 64 bit systems.
Date: Mon, 02 Dec 2013 20:44:00 -0000 [thread overview]
Message-ID: <529CF132.6030000@etr-usa.com> (raw)
In-Reply-To: <529CEDE5.4030703@etr-usa.com>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On 12/2/2013 13:30, Warren Young wrote:
> On 12/2/2013 12:56, Christopher Faylor wrote:
>> On Mon, Dec 02, 2013 at 12:35:00PM -0700, Warren Young wrote:
>>> This happens because POSIX PIDs are in a table that lives in
>>> cygwin1.dll's memory space, and because there are two DLLs, there are
>>> two different PID tables.
>>
>> Actually POSIX pids are Windows PIDs. The distinction becomes fuzzy
>> after an exec, though, where the Cygwin PID continues to be the PID
>> of the process which previously exec'ed it.
>
> Of the four PID values this pair of programs prints, shouldn't at least
> two should be the same, then? I get four different values here:
>
> PARENT: My PID is 5048; created child PID 5684
> CHILD: My PID is 3108; my parent's PID is 1.
I've modified the test programs a bit. The parent can launch either a
32- or 64-bit child, and I've modified the two processes' output so
they're easier to distinguish.
Run without args, parent64 still runs child32, but you can now pass "64"
(i.e. "./parent64 64") to make it run the new child64 program. When you
do that, the output is completely sensible, unlike with the mixed
bitness case:
PARENT64: My PID is 8808; created child PID 3480.
CHILD64: My PID is 3480; my parent's PID is 8808.
Also, doesn't the fact that procps only shows processes running under
the current Cygwin DLL indicate that the process table is DLL-specific?
[-- Attachment #2: child32.cpp --]
[-- Type: text/x-c++src, Size: 169 bytes --]
#include <iostream>
#include <unistd.h>
int main()
{
std::cout << "CHILD32: My PID is " << getpid() <<
"; my parent's PID is " << getppid() << '.' << std::endl;
}
[-- Attachment #3: child64.cpp --]
[-- Type: text/x-c++src, Size: 169 bytes --]
#include <iostream>
#include <unistd.h>
int main()
{
std::cout << "CHILD64: My PID is " << getpid() <<
"; my parent's PID is " << getppid() << '.' << std::endl;
}
[-- Attachment #4: parent64.cpp --]
[-- Type: text/x-c++src, Size: 584 bytes --]
#include <iostream>
#include <unistd.h>
#include <errno.h>
#include <string.h>
int main(int argc, char* argv[])
{
std::cout << "PARENT64: My PID is " << getpid() << "; " << std::flush;
switch (int pid = fork()) {
case -1: // error
std::cout << "ERROR: " << strerror(errno) << std::endl;
break;
case 0: { // child
const char* cmd =
(argc > 1 && strcmp(argv[1], "64") == 0) ?
"./child64" :
"./child32";
execl(cmd, cmd, 0);
break;
}
default: // parent
std::cout << "created child PID " << pid << '.' << std::endl;
}
sleep(1);
}
next prev parent reply other threads:[~2013-12-02 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 20:13 Buchbinder, Barry (NIH/NIAID) [E]
2013-11-27 22:17 ` JonY
2013-11-27 22:27 ` Christopher Faylor
2013-12-02 19:35 ` Warren Young
2013-12-02 19:56 ` Christopher Faylor
2013-12-02 20:30 ` Warren Young
2013-12-02 20:44 ` Warren Young [this message]
2013-12-02 21:07 ` Christopher Faylor
2013-12-17 20:41 ` Christopher Faylor
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=529CF132.6030000@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin-talk@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).