X-Spam-Check-By:	sourceware.org
Message-ID:	<4497EAB0.722D10EF@dessent.net>
Date:	Tue, 20 Jun 2006 05:31:44 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Thread-related segfault with cygwin 1.5.19-4
References:	<GGEHLLAOPBJBGJGBDADHMEBGDJAA DOT jsb AT hal-pc DOT org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
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

"Jon S. Berndt" wrote:

> via various google searches, and asking other developers for help. I
> searched the cygwin mailing list archives, and checked the cygwin FAQ
> ("Known problems ..."). Even though this is not a real cygwin problem, if
> this question gets asked so often, it might be worth adding a response in
> the FAQ.

This particular issue certainly qualifies for the 'F' in FAQ.  It's a
case of SHTDIANH (somebody has to do it and nobody has) though.  The FAQ
tends to not be the greatest place to look for breaking news, and this
one is still relatively recent.

Furthermore, the solution at the moment is rather awkward (build gdb and
Cygwin from CVS), and I'm not sure we'll make any friends by officially
suggesting that procedure right now.  I think to most people that would
read as "just wait until the next release of gdb and Cygwin."

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/

- Raw text -