Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 17 Oct 2002 12:10:25 +0400
From:	egor duda <deo AT logos-m DOT ru>
Reply-To:	egor duda <cygwin AT cygwin DOT com>
Organization:	deo
X-Priority:	3 (Normal)
Message-ID:	<12863202340.20021017121025@logos-m.ru>
To:	Thomas Mellman <tmellman AT web DOT de>
CC:	cygwin AT cygwin DOT com
Subject:	Re: new gdb interface
In-Reply-To:	<200210170756.g9H7umX04188@mailgate5.cinetic.de>
References:	<200210170756 DOT g9H7umX04188 AT mailgate5 DOT cinetic DOT de>
MIME-Version:	1.0

Hi!

Thursday, 17 October, 2002 Thomas Mellman tmellman AT web DOT 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 AT logos-m DOT 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/

- Raw text -