Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 28 Feb 2001 13:54:29 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Make hung in WaitForMultipleObjects inside Cygwin
Message-ID:	<20010228135429.F2327@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20010228155722 DOT 21696 DOT qmail AT lizard DOT curl DOT com>
Mime-Version:	1.0
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

- Raw text -