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 Message-ID: <3D38C828.2050802@hekimian.com> Date: Fri, 19 Jul 2002 22:17:12 -0400 X-Sybari-Trust: 6ab6699e b923d9bf 0879ee9b 00000109 From: Joe Buehler Reply-To: joseph DOT buehler AT spirentcom DOT com Organization: Spirent Communications User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: cygwin hang problem 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> <20020720013040 DOT GA3445 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > 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: That was my change -- to invoke with waitloop == true. At least in the snapshot I am using, the code goes like this: if (try_to_debug(0)) { debugging = 1; return 0; } I observed that "debugging" got quite high in value before dumper managed to attach, and I was concerned that who knows what had been done to the stack in the meanwhile. I am typing this via vnc and a cable modem, so will submit the code change for this later if you want it -- it is an easy enough change. -- Joe Buehler Principal Software Engineer Hekimian Division SPIRENT COMMUNICATIONS 15200 Omega Drive Rockville, MD 20850-3240 USA Phone: +1 301.590.3600 Fax: +1 301.590.3692 www.spirentcom.com