From: Masamichi Hosoda <trueroad@trueroad.jp>
To: cygwin@cygwin.com
Subject: g++ std::map initializing raises segmentation fault.
Date: Thu, 06 Jul 2017 12:26:00 -0000 [thread overview]
Message-ID: <20170706.212622.2189310858003243560.trueroad@trueroad.jp> (raw)
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.
So I suspect cygwin-devel-2.8.1-1 is the cause.
Here's sample code for reproduce.
```
// foo.cc
// g++ -std=c++11 foo.cc
#include<iostream>
#include<map>
std::map<int, int> m
{
{ 1, 1},
{ 2, 2}
};
int main ()
{
std::cout << "Hello World!" << std::endl;
}
```
I've reproduced it on both Windows 7 64 bit and Windows 10 64 bit.
```
$ ./a
Segmentation fault (core dumped)
$
```
Here's my environment.
```
$ uname -a
CYGWIN_NT-10.0 Z87EXTREAM4 2.8.1(0.312/5/3) 2017-07-03 14:11 x86_64 Cygwin
$ g++ --version
g++ (GCC) 5.4.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$
```
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 reply other threads:[~2017-07-06 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 12:26 Masamichi Hosoda [this message]
2017-07-07 12:51 ` Marco Atzeri
2017-07-07 13:35 ` Marco Atzeri
2017-07-07 14:09 ` Masamichi Hosoda
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=20170706.212622.2189310858003243560.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).