X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4AC57AFF.3090004@users.sourceforge.net> Date: Thu, 01 Oct 2009 23:01:03 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com, cygwin-ports-general AT lists DOT sourceforge DOT net Subject: Re: latest libstdc++ causing ffmpeg & mplayer to segfault References: <4AC39420 DOT 20702 AT 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> In-Reply-To: <4AC54EB5.1000103@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 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? Yaakov -- 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