Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 19 Jul 2002 21:30:40 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: cygwin hang problem Message-ID: <20020720013040.GA3445@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <3D32FC00 DOT 5090108 AT hekimian DOT com> <20020719050925 DOT GA24259 AT redhat DOT com> <3D37F0E5 DOT 50F3669B AT yahoo DOT com> <20020719141242 DOT GB27697 AT redhat DOT com> <3D38949C DOT 3090200 AT hekimian DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D38949C.3090200@hekimian.com> User-Agent: Mutt/1.3.23.1i On Fri, Jul 19, 2002 at 06:37:16PM -0400, Joe Buehler wrote: >(I modified handle_exceptions to wait for dumper to do the dump): Why did you feel that you had to modify handle_exceptions to wait for dumper? Since dumper is invoked as a debugger, and your backtrace showed that try_to_debug was invoked with waitloop == true, this code should have been exercised: if (!waitloop) return 1; // wouldn't have hit here SetThreadPriority (hMainThread, THREAD_PRIORITY_IDLE); while (!being_debugged ()) /* spin */; As soon as the process is debugged, it should be stopped. If it isn't immediately stopped, then the Sleep (4000) should catch it. I've never seen a case where gdb was invoked (I don't use dumper, I just have gdb pop up a process) where the process being debugged wasn't stopped in try_to_debug. So, there should be no need to modify anything to wait for anything, AFAICT. If there is such a need, there is a bug that needs to be fixed. cgf