Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 19 Apr 2000 13:49:11 -0400
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Cygwin 1.1.0 gdb troubles
Message-ID: <20000419134911.B15867@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com
References: <C9A8E1D07093D111B76A0000F8C9918A03333088 AT zrtpd003 DOT us DOT nortel DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.8i
In-Reply-To: <C9A8E1D07093D111B76A0000F8C9918A03333088@zrtpd003.us.nortel.com>; from cbjones@nortelnetworks.com on Wed, Apr 19, 2000 at 01:44:53PM -0400

On Wed, Apr 19, 2000 at 01:44:53PM -0400, Christopher Jones wrote:
>>The main reason for cygwin pids is that there is no corresponding
>>exec*() style interface in Win32 land.  Most programs which use
>>fork/exec also rely on the fact that the exec'ed process has the same
>>PID as the fork.  There is no way to do this using the Win32 API.
>
>Thanks for the explanation Chris.  It had been a while since I dealt
>with fork/exec and I'd forgotten how much they rely on a certain PID
>behavior.  So the only other way to go would be to assign win32
>processes cygwin pids which would probably lead to more yuckiness; and
>maybe there is not a way to muck with the internals of windows such
>that cygwin is always resident and receiving notification of new win32
>process/thread creation.  Ick.  Oh well.  :)

I believe that it is possible to wedge cygwin into the process creation
part of Windows NT, at least, but, I dunno... it just seems wrong.

I've been trying hard, since I first started working on cygwin three
years ago, to come up with some way to get rid of the artificial pids,
but so far, I haven't thought of anything.

That's why I'll be so interested in hearing about Paul Sokolovsky's
breakthrough.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com