public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: g++ std::map initializing raises segmentation fault.
Date: Fri, 07 Jul 2017 22:32:00 -0000	[thread overview]
Message-ID: <0183849e-19e3-f040-56bc-3a7c90216b9c@cygwin.com> (raw)
In-Reply-To: <685f073b-833f-2663-0c68-3ac372edf0a5@cornell.edu>

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

  reply	other threads:[~2017-07-07 22:32 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
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 [this message]
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=0183849e-19e3-f040-56bc-3a7c90216b9c@cygwin.com \
    --to=yselkowitz@cygwin.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).