This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: Design mixed 32 and 64 bit systems.
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-talk at cygwin dot com
- Date: Tue, 17 Dec 2013 15:41:42 -0500
- Subject: Re: Design mixed 32 and 64 bit systems.
- Authentication-results: sourceware.org; auth=none
- References: <6CF2FC1279D0844C9357664DC5A08BA21D7054 at MLBXV06 dot nih dot gov> <529CE0E4 dot 4080804 at etr-usa dot com> <20131202195626 dot GC604 at ednor dot casa dot cgf dot cx> <529CEDE5 dot 4030703 at etr-usa dot com> <20131202210551 dot GA2497 at ednor dot casa dot cgf dot cx>
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
- Reply-to: cygwin-talk at cygwin dot com
On Mon, Dec 02, 2013 at 04:05:51PM -0500, Christopher Faylor wrote:
>It's a subtle distinction but there is no real table of Cygwin pids
>maintained by the DLL. Each process has a shared memory region
>associated with it that holds information like the parent pid. This
>shared memory region is not recognized between x86/x86_64.
Just a further clarification for anyone who's interested: There is
a table of child pids maintained by each process. So the DLL does
maintain a list of pids. It just doesn't maintain a list of all
known Cygwin processes.
cgf