public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: worsafe@bellsouth.net
To: cygwin cygwin <cygwin@cygwin.com>
Subject: cygwin gfortran segfaulting on valid write statements
Date: Fri, 17 Apr 2020 13:42:36 -0500	[thread overview]
Message-ID: <d04d793a-6c8b-7a11-5a9b-5cda1bb86e50@bellsouth.net> (raw)
In-Reply-To: <d04d793a-6c8b-7a11-5a9b-5cda1bb86e50.ref@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?


       reply	other threads:[~2020-04-17 18:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d04d793a-6c8b-7a11-5a9b-5cda1bb86e50.ref@bellsouth.net>
2020-04-17 18:42 ` worsafe [this message]
2020-04-17 19:39   ` Marco Atzeri
2020-04-17 22:29     ` Charles Russell
2020-04-17 19:42   ` Brian Inglis
2020-04-17 19:46   ` Brian Inglis
2020-04-17 23:33     ` Charles Russell
2020-04-18  1:01       ` Brian Inglis
     [not found]         ` <f868b6d5-2aee-c314-8a90-ba86a6aeeca6@bellsouth.net>
2020-04-18 16:23           ` gfortran 9.3 write format error (was: segfaulting on valid write statements) Brian Inglis
2020-04-18 17:00             ` gfortran 9.3 write format error Eliot Moss
2020-04-18 18:13             ` Charles Russell
2020-04-18 18:45               ` worsafe
2020-04-18 18:52               ` worsafe
2020-04-18 20:12               ` Charles Russell

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=d04d793a-6c8b-7a11-5a9b-5cda1bb86e50@bellsouth.net \
    --to=worsafe@bellsouth.net \
    --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).