Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 28 Feb 2001 13:54:29 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Make hung in WaitForMultipleObjects inside Cygwin Message-ID: <20010228135429.F2327@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010228155722.21696.qmail@lizard.curl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010228155722.21696.qmail@lizard.curl.com>; from jik@curl.com on Wed, Feb 28, 2001 at 10:57:22AM -0500 On Wed, Feb 28, 2001 at 10:57:22AM -0500, Jonathan Kamens wrote: >Another approach I'm considering is to compile both cygwin1.dll and >make with debugging symbols and install them without stripping. If I >do that, and then Make hangs and I attach to it with gdb, will I >be able to get a useful backtrace showing which call to >WaitForMultipleObjects is hanging and what the various variables >related to that call are? Possibly. There's no way of knowing. You'll have to inspect the states of various threads. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple