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, 17 Oct 2002 12:10:25 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <12863202340.20021017121025@logos-m.ru> To: Thomas Mellman CC: cygwin@cygwin.com Subject: Re: new gdb interface In-Reply-To: <200210170756.g9H7umX04188@mailgate5.cinetic.de> References: <200210170756.g9H7umX04188@mailgate5.cinetic.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Thursday, 17 October, 2002 Thomas Mellman tmellman@web.de wrote: TM> I had to power down my box - neither kill(-9) on either the process under test, TM> the debugger or the debugger window, nor even the task manager were able TM> to kill the two processes, and even windows-shutdown hung. This is (probably) a bug in windows debugging interface. Similar hangs (when one tries to kill debugee or debugger, and then they both remains unkillable) are not gdb specific. They occur with any windows program which exercise debugging APIs. Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/