From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Core dump on 32-bit Cygwin if program calls dlopen
Date: Tue, 15 Jul 2014 15:29:00 -0000 [thread overview]
Message-ID: <20140715152938.GN10401@calimero.vinschen.de> (raw)
In-Reply-To: <CAO1jNwtfhebZsA7fUadApxJSbrmY2KPK1+k7eo3YJvDUmqCoNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Jul 15 16:45, Jan Nijtmans wrote:
> 2014-07-15 16:39 GMT+02:00 Corinna Vinschen:
> > On Jul 15 21:55, JonY wrote:
> >> On 7/15/2014 21:08, Corinna Vinschen wrote:
> >> >>
> >> >> FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.
> >> >
> >> > JonY, do you have a chance to have a look into this issue?
> >> >
> >>
> >> Sorry, I have been busy these few weeks, but I am well aware that there
> >> is a problem with one of the libgcc changes, but has yet to investigate it.
> >>
> >> I believe Jon Turney has looked into it somewhat.
> >
> > Sounds good. Thanks in advance.
>
> Is this essentially the same problem as described here?
>
> <http://gcc.gnu.org/ml/gcc/2013-05/msg00180.html>
I just read the entire thread and it looks pretty much like what we see
here. Eli Zaretskii's analysis of the crash is very enlightening and
seems to hit the nail on its head, but unfortunately there was never any
reply from the guys maintaining the Windows parts of gcc :(
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: 819 bytes --]
next prev parent reply other threads:[~2014-07-15 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 14:45 Jan Nijtmans
2014-07-15 15:29 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-15 13:34 Houder
2014-07-14 23:42 Ken Brown
2014-07-15 9:03 ` Corinna Vinschen
2014-07-15 11:45 ` Ken Brown
2014-07-15 13:08 ` Corinna Vinschen
2014-07-15 13:56 ` JonY
2014-07-15 14:39 ` Corinna Vinschen
2014-07-16 7:02 ` Corinna Vinschen
2014-07-16 22:03 ` JonY
2014-07-17 7:37 ` Corinna Vinschen
2014-07-17 15:31 ` Jon TURNEY
2014-07-17 18:24 ` Corinna Vinschen
2014-07-20 22:02 ` JonY
2014-07-22 8:27 ` Corinna Vinschen
2014-07-22 13:00 ` Jon TURNEY
2014-07-22 13:20 ` Corinna Vinschen
2014-07-24 13:08 ` Kai Tietz
2014-07-24 13:45 ` Corinna Vinschen
2014-07-24 22:15 ` JonY
2014-07-25 12:37 ` 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=20140715152938.GN10401@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).