public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
Date: Fri, 07 Nov 2014 09:32:00 -0000	[thread overview]
Message-ID: <545C919D.4070706@gmail.com> (raw)
In-Reply-To: <545BFD6B.8060000@free.fr>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On 11/7/2014 06:59, Falk Tannhäuser wrote:
> Am 06.11.2014 um 23:37 schrieb JonY:
>> On 11/7/2014 05:06, Falk Tannhäuser wrote:
>>> Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error
>>>        collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet
>>> when compiling and linking a C or C++ program. However, an executable is
>>> generated and appears to work as expected.
>>> I installed the latest test release of cygwin so far (1.7.33-0.7).
>>
>> Does it somehow work if you link with gcc -fno-lto?
> 
> Yes, this fixes the problem.
> 

There seems to be some confusion in the __cxa_atexit in Cygwin 1.7.32,
basically 4.9.1 will only work with .32.

1.7.33 fixed the incorrect behavior that unfortunately broke gcc
__cxa_atexit usage. The next 1.7.33-0.8 should be more tolerant of the
old .32 behavior.

After 1.7.33 is officially released, gcc-4.8.3-4 and 4.9 will switch to
the standard conformant behavior.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2014-11-07  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <545BE242.7020507@free.fr>
2014-11-06 21:06 ` Falk Tannhäuser
2014-11-06 22:37   ` JonY
2014-11-06 22:59     ` Falk Tannhäuser
2014-11-07  9:32       ` JonY [this message]
2014-11-07 20:42         ` Falk Tannhäuser

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=545C919D.4070706@gmail.com \
    --to=10walls@gmail.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).