Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Thu, 11 May 2000 14:14:50 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: GCC snapshots and mmap problem [Re: GDB hangs on Win2K]
Message-ID: <20000511141450.B929@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com
References: <200005111710.NAA24928@envy.delorie.com> <200005111720.MAA19448@hp2.xraylith.wisc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <200005111720.MAA19448@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Thu, May 11, 2000 at 12:20:11PM -0500

On Thu, May 11, 2000 at 12:20:11PM -0500, Mumit Khan wrote:
>Can someone check if the problem goes away with thread-disabled Cygwin
>DLL? Note that in my case it's hanging in munmap (unless it's also
>popping up a window on the local box, which I can't see when logged on
>remotely, sigh), which may point to a Cygwin waiting on a lock. Cygwin
>currently uses a single resource lock, even though the basic framework 
>for using multiple locks is there via LOCK_ macros, so a single mismatched
>Set/Release lock may cause problems. I can't check currently since I'm 
>connecting to my home net via modem, and don't have gcc on my laptop.

I don't understand.  If gcc is hung waiting for a resource lock, that
will be made very clear by attaching gdb to the hung process.

I don't see why we have to go the the pain of attempting a rebuild of
cygwin as a debugging technique.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com