X-Spam-Check-By: sourceware.org Date: Mon, 8 May 2006 02:44:37 -0700 From: clayne AT anodized DOT com To: cygwin AT cygwin DOT com Subject: Re: pthread_mutex_init + gdb issue again Message-ID: <20060508094437.GC18330@ns1.anodized.com> References: <20060508084139 DOT GB18330 AT ns1 DOT anodized DOT com> <445F08CC DOT 4375998F AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445F08CC.4375998F@dessent.net> User-Agent: Mutt/1.5.11 X-Assp-Spam-Prob: 0.00000 X-Assp-Whitelisted: Yes X-Assp-Envelope-From: clayne AT ns1 DOT anodized DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, May 08, 2006 at 02:01:00AM -0700, Brian Dessent wrote: > > Rather than work-arounds, why not just use a recent build of gdb that > doesn't suffer from this problem? The issue was fixed in CVS earlier > this year. But do note that it requires functionality not present in > Cygwin 1.5.19, so you'll also need to use a recent Cygwin snapshot. Thanks. I'll look into it. My workaround isn't a proper workaround after all anyways. -cl -- 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/