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

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

[Ivan Gagis]

Hi,

I'm having the same problem after updating to latest cygwin packages.
It seems quite important problem, are there any plans to fix it?

Trying to debug the test program from Masamichi Hosoda it can be seen
that crash occurs in std::map implementation, see stacktrace below. I
wonder if there was any update to STL recently in cygwin?


Program received signal SIGSEGV, Segmentation fault.
0x0000000100401bf4 in std::less<int>::operator()(int const&, int
const&) const ()
(gdb) bt
#0  0x0000000100401bf4 in std::less<int>::operator()(int const&, int
const&) const ()
#1  0x00000001004028dd in std::_Rb_tree<int, std::pair<int const,
int>, std::_Select1st<std::pair<int const, int> >, std::less<int>,
std::allocator<std::pair<int const, int> >
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator<std::pair<int
const, int> >, int const&) ()
#2  0x0000000100402685 in std::_Rb_tree_iterator<std::pair<int const,
int> > std::_Rb_tree<int, std::pair<int const, int>,
std::_Select1st<std::pair<int const, int> >, std::less<int>,
std::allocator<std::pair<int const, int> >
>::_M_insert_unique_<std::pair<int const, int> const&,
std::_Rb_tree<int, std::pair<int const, int>,
std::_Select1st<std::pair<int const, int> >, std::less<int>,
std::allocator<std::pair<int const, int> >
>::_Alloc_node>(std::_Rb_tree_const_iterator<std::pair<int const, int>
>, std::pair<int const, int> const&, std::_Rb_tree<int, std::pair<int
const, int>, std::_Select1st<std::pair<int const, int> >,
std::less<int>, std::allocator<std::pair<int const, int> >
>::_Alloc_node&) ()
#3  0x0000000100402579 in void std::_Rb_tree<int, std::pair<int const,
int>, std::_Select1st<std::pair<int const, int> >, std::less<int>,
std::allocator<std::pair<int const, int> >
>::_M_insert_unique<std::pair<int const, int> const*>(std::pair<int
const, int> const*, std::pair<int const, int> const*) ()
#4  0x0000000100401fec in std::map<int, int, std::less<int>,
std::allocator<std::pair<int const, int> >
>::map(std::initializer_list<std::pair<int const, int> >,
std::less<int> const&, std::allocator<std::pair<int const, int> >
const&) ()
#5  0x00000001004011a8 in __static_initialization_and_destruction_0(int, int) ()
#6  0x000000010040120a in _GLOBAL__sub_I_m ()
#7  0x0000000180045ef5 in do_global_ctors (force=0,
in_pfunc=0x100402ec0 <___CTOR_LIST__>) at
/usr/src/debug/cygwin-2.8.1-1/winsup/cygwin/dcrt0.cc:77
#8  __main () at /usr/src/debug/cygwin-2.8.1-1/winsup/cygwin/dcrt0.cc:1128
#9  0x00000001004010ed in main ()

Br,
Ivan

>
> From: Masamichi Hosoda <trueroad at trueroad dot jp>
> 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-results: sourceware.org; auth=none
>
>
> 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

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

[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 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.
>>
>> I've just checked that the problem occurs with the 2017-06-20 snapshot 
>> but not with the 2017-06-06 snapshot.
> 
> I did the bisection:
> 
> 6a6c1c52e6bfea85beb06ea60417b90ae3c6857c is the first bad commit
> commit 6a6c1c52e6bfea85beb06ea60417b90ae3c6857c
> Author: Yaakov Selkowitz <yselkowi@redhat.com>
> Date:   Tue Jun 13 14:58:33 2017 -0500
> 
>      Feature test macros overhaul: Cygwin signal.h
> 
>      This should match newlib's <sys/signal.h>.

Ken, thank you for bisecting this.  I'm testing a fix now.

-- 
Yaakov

--
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

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

[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_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)
> 
> I've just checked that the problem occurs with the 2017-06-20 snapshot 
> but not with the 2017-06-06 snapshot.  I don't have time right now to do 
> a further bisection, but I can probably do it later today or over the 
> weekend if no one beats me to it.

I did the bisection:

6a6c1c52e6bfea85beb06ea60417b90ae3c6857c is the first bad commit
commit 6a6c1c52e6bfea85beb06ea60417b90ae3c6857c
Author: Yaakov Selkowitz <yselkowi@redhat.com>
Date:   Tue Jun 13 14:58:33 2017 -0500

     Feature test macros overhaul: Cygwin signal.h

     This should match newlib's <sys/signal.h>.

Ken

--
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

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

[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 dumped)



Even if g++ 6.3.0-2 with `-std=c++11`,
there is no problem if cygwin-devel-2.8.0-1 is installed.



```
$ uname -a
CYGWIN_NT-10.0 inspiron5559 2.8.1(0.312/5/3) 2017-07-03 14:11 x86_64 Cygwin

$ cygcheck -c cygwin-devel
Cygwin Package Information
Package              Version        Status
cygwin-devel         2.8.0-1        OK

$ g++ --version
g++ (GCC) 6.3.0
Copyright (C) 2016 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.


$ g++ -std=c++11 foo.cc

$ ./a
Hello World!

$ g++ -std=gnu++11 foo.cc

$ ./a
Hello World!

$
```



However, if cygwin-devel-2.8.1-1 is installed, segmentation fault is raised.



```
$ uname -a
CYGWIN_NT-10.0 inspiron5559 2.8.1(0.312/5/3) 2017-07-03 14:11 x86_64 Cygwin

$ cygcheck -c cygwin-devel
Cygwin Package Information
Package              Version        Status
cygwin-devel         2.8.1-1        OK

$ g++ --version
g++ (GCC) 6.3.0
Copyright (C) 2016 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.


$ g++ -std=c++11 foo.cc

$ ./a
Segmentation fault (core dumped)

$ g++ -std=gnu++11 foo.cc

$ ./a
Hello World!

$
```



So the cause is cygwin-devel-2.8.1-1 in my humble opinion.

--
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

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

[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-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)

I've just checked that the problem occurs with the 2017-06-20 snapshot 
but not with the 2017-06-06 snapshot.  I don't have time right now to do 
a further bisection, but I can probably do it later today or over the 
weekend if no one beats me to it.

Ken


--
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

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

[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:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

[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 <trueroad@trueroad.jp>:
>> 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
>

--
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

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

[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
>>> 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

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

[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_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

Regards
Marco

--
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

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

[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-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)
>

I can not replicate.

$ uname -svr
CYGWIN_NT-6.1 2.8.1(0.312/5/3) 2017-07-03 14:11

$ ./a.exe
Hello World!


Please provide your cygcheck.out as attachment
> Problem reports:       http://cygwin.com/problems.html

--
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

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

[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 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