From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin gfortran segfaulting on valid write statements
Date: Fri, 17 Apr 2020 13:46:54 -0600 [thread overview]
Message-ID: <e7cdd735-aa29-b255-e643-eb35e5f6693d@SystematicSw.ab.ca> (raw)
In-Reply-To: <d04d793a-6c8b-7a11-5a9b-5cda1bb86e50@bellsouth.net>
On 2020-04-17 12:42, worsafe@bellsouth.net wrote:
> 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.
Try running under strace:
$ strace -o prog.strace prog -options... args...
or gdb:
$ gdb prog
(gdb) run -options... args...
SEGV diagnostics
(gdb) bt
(gdb) q
and attach or paste all output.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
next prev parent reply other threads:[~2020-04-17 19:46 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
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 [this message]
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=e7cdd735-aa29-b255-e643-eb35e5f6693d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).