X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=Yx49CAaoxLsggVIKjHapXiQbdH1t97ohyTZ3oVuI2q2/ZoUL0VH7h
	v9+MqZKvWf8U8yQYSNAuMJqIwAh/sA/Qb8vxM8wA1c06ayfK2t56hgTMBRcpZ1U1
	3uGPWpIT7E/j84/JjEno+Rb35y7VRD2T+cp+V/451C9x1iCoJZGi1A=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=j/dX+hfRhrCP2uoIFHK2TKWj1lA=; b=cMqG+7x7ROoO5NA0Mm6EeXhHxlEL
	B1Ap8IDN3nGoj7OCeq8nP2PiGAg1eHkK2c7TfPNeyYnKknEM4naB+bfbuXb58yy2
	spBQyoLyhjQnyv7ME/58MMa605/0+7XCgNYtITXy4lEbE3r6W5MbOGyCwD0bRpwn
	lwxmtPiaD+FaEU0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	Jean-Pierre Flori <jpflori AT gmail DOT com>
Subject:	Re: python aborts
Date:	Wed, 6 Nov 2013 22:30:02 +0000 (UTC)
Lines:	56
Message-ID:	<l5efta$5qf$1@ger.gmane.org>
References:	<51F0CF92 DOT 60009 AT dancol DOT org> <51F0E39C DOT 1090500 AT dancol DOT org> <20130725091741 DOT GA20682 AT calimero DOT vinschen DOT de> <51F0FB68 DOT 90904 AT gmail DOT com> <51F103CB DOT 20904 AT gmail DOT com> <20130725151410 DOT GB6932 AT ednor DOT casa DOT cgf DOT cx> <51F14DE9 DOT 7050702 AT gmail DOT com> <20130725172007 DOT GC6019 AT ednor DOT casa DOT cgf DOT cx> <51F1A3AA DOT 5040804 AT gmail DOT com> <20130726031048 DOT GD1954 AT ednor DOT casa DOT cgf DOT cx> <20130828035943 DOT GA6973 AT ednor DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
User-Agent:	Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2)
X-IsSubscribed:	yes

Dear all,

Le Tue, 27 Aug 2013 23:59:43 -0400, Christopher Faylor a écrit :

> On Thu, Jul 25, 2013 at 11:10:48PM -0400, Christopher Faylor wrote:
>>On Fri, Jul 26, 2013 at 06:16:10AM +0800, JonY wrote:
>>>On 7/26/2013 01:20, Christopher Faylor wrote:
>>>> On Fri, Jul 26, 2013 at 12:10:17AM +0800, JonY wrote:
>>>>> On 7/25/2013 23:14, Christopher Faylor wrote:
>>>>>>
>>>>>> I'm still a (silent) gcc maintainer so I can presumably accept this
>>>>>> patch.
>>>>>>
>>>>>> Are there outstanding patches that need attention?  If so, please
>>>>>> send URLs from the gcc-patches archive here so that I can attend to
>>>>>> them.
>>>>>>
>>>>>>
>>>>> This libgcc patch, and some minor patches at
>>>>> http://gcc.gnu.org/ml/gcc-patches/2013-07/msg00416.html.
>>>>>
>>>>> There are some others from Yaakov's gcc builds, but let's start with
>>>>> smaller patches first.
>>>> 
>>>> It will probably be a couple of days before I can give these adequate
>>>> attention.
>>>> 
>>>> Ok to submit your name as an upstream approver, JonY?
>>>> 
>>>> 
>>>I have not approved any patches for GCC, not sure if I can act as
>>>approver. Kai usually approves and commits any mingw* related gcc
>>>patches but he is not in currently.
>>
>>Uh, yeah.  AFAIK, you aren't listed as a package approver so it would be
>>very difficult for you to approve anything.
>>
>>Ok, nevermind.
> 
> Did this ever get resolved?  Did Kai apply the patches?
> 
> cgf

Any progress on this very nasty libgcc bug?
I've been struggling with random python aborts in the last past weeks, 
pointing more or less to verifyable_object_isvalid with quite unhelpful 
backtraces, when I finally found this report and a potential fix at 
http://cygwin.com/ml/cygwin/2013-07/msg00528.html.
See also http://cygwin.com/ml/cygwin/2013-08/msg00201.html.
The fix seems to do the trick for me though I cannot really rely on any 
Cygwin part linked with cyggcc_s.dll unless I recompile it.
Any plan to trigger a complete rebuild of Cygwin packages using a fixed 
GCC? :)

Best,
JP


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