X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Fri, 2 Oct 2009 01:39:50 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: latest libstdc++ causing ffmpeg & mplayer to segfault
Message-ID:	<20091002053950.GC23109@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<a07c15f00909300907v3b550276o7511fea29255832d AT mail DOT gmail DOT com> <4AC39420 DOT 20702 AT gmail DOT com> <a07c15f00910010713n24c387efm1d192e26d064e455 AT mail DOT gmail DOT com> <4AC527D3 DOT 6050106 AT gmail DOT com> <4AC52F4B DOT 6090701 AT users DOT sourceforge DOT net> <4AC5350F DOT 8050105 AT gmail DOT com> <4AC54EB5 DOT 1000103 AT gmail DOT com> <4AC57AFF DOT 3090004 AT users DOT sourceforge DOT net>
MIME-Version:	1.0
In-Reply-To:	<4AC57AFF.3090004@users.sourceforge.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Thu, Oct 01, 2009 at 11:01:03PM -0500, Yaakov (Cygwin/X) wrote:
>On 01/10/2009 19:52, Dave Korn wrote:
>>    Correction: the fixes in the snapshot are sufficient for now, and will allow
>> mplayer to work.  (There appears to be something else buggy on head that was
>> confounding my efforts to test a fix.)
>>
>>    There is still I think a potential loophole that we just haven't done
>> anything complex to run up enough against yet, but it's not going to cause
>> trouble this week, I think.
>
>Am I correct that the real fix for this is simply rebuilding with a new 
>enough libcygwin.a?  And exactly which versions were faulty?

Yes, you're correct.

I posted the faulty versions a while ago:

On Mon, Sep 21, 2009 at 10:48:27AM -0400, Christopher Faylor wrote:
>I can say that any DLL built with cygwin-1.7.0-51 - cygwin-1.7.0-56
>is probably suspect.  That's 2009-07-13 - 2009-08-13 .

cgf

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

- Raw text -