From mboxrd@z Thu Jan  1 00:00:00 1970
From: jmm@raleigh.ibm.com
To: john@exmachina.net (John Mullee)
Cc: gnu-win32@cygnus.com
Subject: Re: pid problem found
Date: Sun, 28 Feb 1999 23:02:00 -0000
Message-ID: <199902081430.JAA25094@jmm.raleigh.ibm.com>
References: <36BEF2B3.4A3B0C4C@exmachina.net>
X-SW-Source: 1999-02n/msg00214.html
Message-ID: <19990228230200.JKgPDhjx4FUKYSqjbc4nmSnsc0bAA_k8qOkwiDxMyJs@z>

> 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.

Thanks for all your help,

James Manning
-- 
Hardware Design Engineer --- IBM Netfinity Performance Development

--   
Want to unsubscribe from this list?                             
Send a message to cygwin-unsubscribe@sourceware.cygnus.com