From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by sourceware.org (Postfix) with ESMTPS id 2CAE0385C426 for ; Fri, 17 Apr 2020 19:40:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2CAE0385C426 Received: by mail-wm1-x32b.google.com with SMTP id v8so5672669wma.0 for ; Fri, 17 Apr 2020 12:40:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=YURxhj5wdezRBGwojw3Y3/bhJFcN72LpQmLDB8YSZow=; b=LzhxIb2mQ8u2SBFXH6vNuWcZ2PGG+FybDfHJrWCtilOBoycsRZFgCbMqktZ9WRoshT UvZVo1Oo0evokwcHO9Op+Uel+Y2nXRu1zMTR9AVfd4WHlCKVakngWBt5qi6wKdSn6azZ BMGBiacPkAq/Kb36ShTKXKfVUHWAY+hN9UoCIoZjiCo3y8c41ieGwlUlfMFXepUvBpIc ZitLZraQQmBhvLmRyUh1anRUo0A3toLW2M1XvvpPXvSOrsT1kTQa48kLchaFrbwhaJCE b7cCStLX2vcQEahG5GSCPSmFKi4150XwbB/ipWDqgMXy/iDLN5JmbB/RnJrnLI+uMh9A oqUA== X-Gm-Message-State: AGi0PuZaL7ff7cny6NkXjyyo0HWwY7ZRe0XftUAgrGRBHiITbwSklnAF Dg9U4rxVp3k+Mqt91O6A6I9BkcPE X-Google-Smtp-Source: APiQypJMGeRdp4HUOJSBF/YPl61apv+cmxEN1aC0hcCDpVOfv6tkhFE85wuJxClxfr/0lt6VafwpWQ== X-Received: by 2002:a7b:c7d2:: with SMTP id z18mr4846554wmk.109.1587152400822; Fri, 17 Apr 2020 12:40:00 -0700 (PDT) Received: from ?IPv6:2003:ee:6717:5001:1430:44a5:66cc:67a5? (p200300EE67175001143044A566CC67A5.dip0.t-ipconnect.de. [2003:ee:6717:5001:1430:44a5:66cc:67a5]) by smtp.gmail.com with ESMTPSA id f83sm9182013wmf.42.2020.04.17.12.39.59 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Apr 2020 12:40:00 -0700 (PDT) Subject: Re: cygwin gfortran segfaulting on valid write statements To: cygwin@cygwin.com References: From: Marco Atzeri Message-ID: <35fe63d9-b708-8e3b-3cc8-51ab0c7e5025@gmail.com> Date: Fri, 17 Apr 2020 21:39:58 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, FREEMAIL_REPLY, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 19:40:03 -0000 Am 17.04.2020 um 20:42 schrieb worsafe@bellsouth.net: > I'm getting segfaults in valid write statements Using current cygwin > gfortran (--version reports 9.3.0). This is with old code that runs on > current debian stable and was running on cygwin a few years ago. I have > been unable to construct a simple example for a bug report. > > I would like to try downgrading the gfortran version, but see 6 > different versions of gcc-fortran and 11 versions of libgfortran in the > cygwin repository. Can someone recommend a combination? > 9.3.0-1 libgfortran5 9.2.0-3 libgfortran5 9.2.0-2 libgfortran5 9.2.0-1 libgfortran5 8.3.0-1 libgfortran5 7.4.0-1 libgfortran4 in what type of statement have you the segfault ? Regards Marco