On Nov  6 22:30, Jean-Pierre Flori wrote:
> 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 pinged the upstream maintainer who probably wasn't aware of this yet.

> 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? :)

That won't happen, probably, since practically all crucial parts of the
distro are linked dynamically against libgcc.  Just providing and using
a new libgcc should be sufficient, except in rare cases.  AFAIU.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat