Message-ID: <445F216C.69EB1B52@dessent.net>
Date: Mon, 08 May 2006 03:46:04 -0700
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: pthread_mutex_init + gdb issue again
References: <20060508084139.GB18330@ns1.anodized.com> <445F08CC.4375998F@dessent.net> <20060508094437.GC18330@ns1.anodized.com> <20060508102904.GD18330@ns1.anodized.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

clayne@anodized.com wrote:

> Thanks Brian, much better. The issue was that I could not find any reference
> to the problem ever being fixed - just a lot of threads where people were
> ending with "yea you gotta hit continue - it sucks."

Right.  It was reported often, and because of that there was a lot of
noise, and if you weren't following the patches going into cygwin and
gdb it would be easy to overlook as there wasn't exactly fanfare.

I expect that after 1.5.20 is out the door an updated gdb binary package
will happen, and hopefully at that point it will be a lot easier to say
"use the new version, see the release announcement" compared to "build
it yourself from CVS".

Brian

--
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/