Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id:	<199903112254.QAA28109@modi.xraylith.wisc.edu>
X-Authentication-Warning:	modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: Repost: process table shows already killed processes
In-reply-to:	Your message of "Thu, 11 Mar 1999 11:14:21 EST."
	<19990311111421 DOT A887 AT cygnus DOT com>
Date:	Thu, 11 Mar 1999 16:54:16 -0600
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> I can't explain the behavior (which is why I haven't responded) but
> I can point out that if you are using some non-cygwin utility to kill
> the processes then the processes won't be able to clean themselves
> out of the cygwin process table.

This point is very important -- the NT kill program will *not* detach
any DLLs, and you may end up in an inconsistent, or at the very least,
a confused state. This took me a while to figure out (and of course 
found the MSDJ article right after ...).

The MS docs do talk about the "right" way to kill, and TerminateProcess
as used by KILL.EXE is not it.

Regards,
Mumit

- Raw text -