Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Wed, 19 Apr 2000 12:47:24 -0400 To: "'cygwin@sourceware.cygnus.com'" Subject: Re: Cygwin 1.1.0 gdb troubles Message-ID: <20000419124724.A15213@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, "'cygwin@sourceware.cygnus.com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from cbjones@nortelnetworks.com on Wed, Apr 19, 2000 at 09:01:38AM -0400 On Wed, Apr 19, 2000 at 09:01:38AM -0400, Christopher Jones wrote: >Seems like it would make more sense to at least hide these cygwin pids >and let users always use windows pids for ps, kill, $$ in a shell, etc. >So the PID and PPID values would be the real windows values and cygwin >pids would disappear into the internals somewhere... probably a lookup >table if you really need to have them still. Something like this would >be more seemless, wouldn't it? 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. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com