Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Bash hangs in WaitForMultipleObjects
Date:	Mon, 14 Jun 2004 11:10:04 +0100
MIME-Version:	1.0
In-Reply-To:	<W840768165265551087184494@webmail1>
Message-ID:	<NUTMEGVp20N39x6HHGN00000330@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	14 Jun 2004 10:10:04.0500 (UTC) FILETIME=[C3163140:01C451F7]

> -----Original Message-----
> From: cygwin-owner On Behalf Of jreif
> Sent: 14 June 2004 04:42

> Below are more traces of the bash processes hanging on my machine.

  Stack backtraces aren't any use without compiling both bash and the cygwin
.dll from source, using the "-g" flag to put debug information into the
compiled output.  Then the stack backtraces will contain accurate function
names; what you see there is nearest-known-externally-visible-symbol guesses
from gdb.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -