Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Yaakov Selkowitz
On 2017-07-07 15:43, Ken Brown wrote: On 7/7/2017 11:12 AM, Ken Brown wrote: On 7/6/2017 8:26 AM, Masamichi Hosoda wrote: 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 faul

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Ken Brown
On 7/7/2017 11:12 AM, Ken Brown wrote: On 7/6/2017 8:26 AM, 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_6

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Masamichi Hosoda
> On 07/07/2017 16:21, Ivan Gagis wrote: >> I installed g++ 6.3.0-2 and still can reproduce the segfault :(. >> >> Br, >> Ivan >> > > It seems due to the -std=c++11 restriction > > $ g++ foo.cc > > $ ./a.exe > Hello World! > > $ g++ -std=c++11 foo.cc > > $ ./a.exe > Segmentation fault (core du

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Ken Brown
On 7/6/2017 8:26 AM, 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. So I suspect cygwin-dev

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Marco Atzeri
On 07/07/2017 16:21, Ivan Gagis wrote: I installed g++ 6.3.0-2 and still can reproduce the segfault :(. Br, Ivan It seems due to the -std=c++11 restriction $ g++ foo.cc $ ./a.exe Hello World! $ g++ -std=c++11 foo.cc $ ./a.exe Segmentation fault (core dumped) -- Problem reports: ht

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Ivan Gagis
I installed g++ 6.3.0-2 and still can reproduce the segfault :(. Br, Ivan 2017-07-07 17:09 GMT+03:00 Masamichi Hosoda : >> 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 initializi

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Masamichi Hosoda
> 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 >>

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Marco Atzeri
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

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Marco Atzeri
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. So I suspect cygwin-dev

Re: g++ std::map initializing raises segmentation fault.

2017-07-07 Thread Ivan Gagis
rc/debug/cygwin-2.8.1-1/winsup/cygwin/dcrt0.cc:1128 #9 0x0001004010ed in main () Br, Ivan > > From: Masamichi Hosoda > To: cygwin at cygwin dot com > Date: Thu, 06 Jul 2017 21:26:22 +0900 (JST) > Subject: g++ std::map initializing raises segmentation fault. > Authentication-

g++ std::map initializing raises segmentation fault.

2017-07-06 Thread Masamichi Hosoda
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 fo