From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: python aborts
Date: Thu, 07 Nov 2013 13:20:00 -0000 [thread overview]
Message-ID: <20131107132020.GA16306@calimero.vinschen.de> (raw)
In-Reply-To: <l5efta$5qf$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2672 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-07 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:11 Denis Excoffier
2013-05-22 12:31 ` Corinna Vinschen
2013-07-25 8:28 ` Daniel Colascione
2013-07-25 8:36 ` Daniel Colascione
2013-07-25 10:18 ` Daniel Colascione
2013-07-25 10:54 ` Corinna Vinschen
2013-07-25 12:12 ` JonY
2013-07-25 13:02 ` JonY
2013-07-25 15:36 ` Christopher Faylor
2013-07-25 17:20 ` JonY
2013-07-25 17:47 ` Christopher Faylor
2013-07-25 22:36 ` JonY
2013-07-26 4:14 ` Christopher Faylor
2013-08-28 3:59 ` Christopher Faylor
2013-11-06 22:30 ` Jean-Pierre Flori
2013-11-07 13:20 ` Corinna Vinschen [this message]
2013-11-07 21:55 ` Jean-Pierre Flori
2013-11-08 16:40 ` Jean-Pierre Flori
2013-11-11 12:59 ` Corinna Vinschen
2013-11-11 13:02 ` JonY
2013-11-11 13:08 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131107132020.GA16306@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).