Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 11 Nov 2004 15:47:14 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: howto register process Message-ID: <20041111204714.GC17251@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <87u0rwury2.fsf@zlatenlist.homelinux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Nov 11, 2004 at 08:05:07PM -0000, Dave Korn wrote: >>kill() prints int STDERR the error message - it is not returned by it. > >That strikes me as very very wrong indeed for a library function. A >quick scan through signal.cc doesn't seem to show anything in kill, >kill0, or kill_worker, that would have that effect, though as always >with C++, an awful lot of the detail can be hidden inside implied >constructors or overloaded operators. Are you _quite_ sure you're >calling cygwin's kill? The only time that cygwin prints anything to stderr is when there is a serious problem in the DLL. In most cases this causes the application to die. kill() is certainly not supposed to be printing "no such pid" type of messages on stderr. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/