From: Masamichi Hosoda <trueroad@trueroad.jp>
To: cygwin@cygwin.com
Subject: Re: g++ std::map initializing raises segmentation fault.
Date: Fri, 07 Jul 2017 14:09:00 -0000 [thread overview]
Message-ID: <20170707.230903.2208998970191971739.trueroad@trueroad.jp> (raw)
In-Reply-To: <5aeb55b6-1c71-bf68-3f2c-31f55bba438e@gmail.com>
> On 07/07/2017 14:51, Marco Atzeri wrote:
>> On 06/07/2017 14:26, Masamichi Hosoda wrote:
>>> Hello,
>>>
>>> On Cygwin 2.8.1 x86_64, I've found that g++ std:map initializing
>>> may raise segmentation fault.
>>> The binary compiled with cygwin-devel-2.8.0-1
>>> does not raise segmentation fault
>>> even if on Cygwin 2.8.1 x86_64 environments.
>>>
>>
>> I can not replicate.
>>
>
> Wrong. I can replicate.
>
> One solution is to use the gcc-6.3.0-2 compiler in test
>
> https://www.cygwin.com/ml/cygwin-announce/2017-06/msg00079.html
Thank you for your information.
If I understand correctly, there is three workaround solutions.
. Use g++ option `-std=gnu++11` instead of `-std=c++11`
TANNHAUSER Falk reported in
https://cygwin.com/ml/cygwin/2017-07/msg00089.html
I've tried this. It works fine.
. Downgrade `cygwin-devel` to 2.8.0-1 instead of 2.8.1-1.
I reported in
https://cygwin.com/ml/cygwin/2017-07/msg00088.html
Of course, it works fine in my environment.
. Use gcc-6.3.0-2 instead of gcc-5.4.0-1
You reported in
https://cygwin.com/ml/cygwin/2017-07/msg00109.html
I'd like to try this.
Thanks
--
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
next prev parent reply other threads:[~2017-07-07 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 12:26 Masamichi Hosoda
2017-07-07 12:51 ` Marco Atzeri
2017-07-07 13:35 ` Marco Atzeri
2017-07-07 14:09 ` Masamichi Hosoda [this message]
2017-07-07 14:21 ` Ivan Gagis
2017-07-07 14:28 ` Marco Atzeri
2017-07-07 16:01 ` Masamichi Hosoda
2017-07-07 15:12 ` Ken Brown
2017-07-07 20:43 ` Ken Brown
2017-07-07 22:32 ` Yaakov Selkowitz
2017-07-07 12:09 Ivan Gagis
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=20170707.230903.2208998970191971739.trueroad@trueroad.jp \
--to=trueroad@trueroad.jp \
--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).