delorie.com/archives/browse.cgi | search |
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: | jmm AT raleigh DOT ibm DOT com |
Message-Id: | <199902081443.JAA25182@jmm.raleigh.ibm.com> |
Subject: | Re: pid problem found |
To: | cgf AT cygnus DOT com (Christopher Faylor) |
Date: | Mon, 8 Feb 1999 09:43:23 -0500 (EST) |
Cc: | jmm AT raleigh DOT ibm DOT com, john AT exmachina DOT net, gnu-win32 AT cygnus DOT com |
In-Reply-To: | <19990208093853.A24123@cygnus.com> from "Christopher Faylor" at Feb 8, 99 09:38:53 am |
> Umm. Cygwin supports anonymous pipes. Think UNIX. That's what we're > trying to emulate. True enough... I should have said "Anon pipes created with CreatePipe and DuplicateHandle and inherited through CreateProcess"... unless I can swap out CreateProcess and the other stuff works (not saying that's not the case, just can't find an API call that claims to do this), then it's code re-write either way, and I might as well move the signal handling stuff over to events since that's pretty small code already (like I said, print an int and exit :) Thanks again, James -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |