Delivered-To:	listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	Christopher Faylor <cgf AT cygnus DOT com>
Message-ID:	<19990208093853.A24123@cygnus.com>
Date:	Mon, 8 Feb 1999 09:38:53 -0500
To:	jmm AT raleigh DOT ibm DOT com, John Mullee <john AT exmachina DOT net>
Cc:	gnu-win32 AT cygnus DOT com
Subject:	Re: pid problem found
References:	<36BEF2B3 DOT 4A3B0C4C AT exmachina DOT net> <199902081430 DOT JAA25094 AT jmm DOT raleigh DOT ibm DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.93i
In-Reply-To:	<199902081430.JAA25094@jmm.raleigh.ibm.com>; from jmm@raleigh.ibm.com on Mon, Feb 08, 1999 at 09:30:55AM -0500

On Mon, Feb 08, 1999 at 09:30:55AM -0500, jmm AT raleigh DOT ibm DOT com wrote:
>> Would it be possible that this 'pid' is something other
>> than that id seen in taskmanager? does cygwin's
>> waitpid use the CreateProcess-pid? or something else?
>
>That was it, as it turns out... CreateProcess returns a Windows pid,
>not a cygwin pid, so cygwin1.dll's waitpid couldn't use it...
>
>Unfortunately, I was using CreateProcess to do anonymous pipe inheritance
>so each of the children could feed back an integer after getting a
>SIGALRM and exit.
>
>What this means now is that I'm stuck either converting the signal(),
>alarm(), and waitpid() stuff to Win32 calls (events I guess) or trying
>to dump all the anon pipe stuff in favor of some other IPC mechanism
>(most likely moving to the Win32 event stuff, I'd guess, though all the
>examples that I've seen do explicit checks for incoming messages in the
>code and not something as simple as installing a handler to print one
>integer and exit.

Umm.  Cygwin supports anonymous pipes.  Think UNIX.  That's what we're
trying to emulate.

cgf

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

- Raw text -