public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/95104] [9/10 Regression] Segfault on a legal WAIT statement
Date: Wed, 27 May 2020 19:08:32 +0000 [thread overview]
Message-ID: <bug-95104-4-kFAfLvxmyr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95104-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95104
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:6f64bc18a664e1d003120cfa8508cb5fe06fa7ad
commit r9-8629-g6f64bc18a664e1d003120cfa8508cb5fe06fa7ad
Author: Harald Anlauf <anlauf@gmx.de>
Date: Tue May 26 23:29:52 2020 +0200
PR fortran/95104 - Segfault on a legal WAIT statement
Referencing a unit in a WAIT statement that has not been opened before
resulted in a NULL pointer dereference. Check for this condition.
2020-05-26 Harald Anlauf <anlauf@gmx.de>
libgfortran/
PR libfortran/95104
* io/transfer.c (st_wait_async): Do not dereference NULL pointer.
gcc/testsuite/
PR libfortran/95104
* gfortran.dg/pr95104.f90: New test.
Co-Authored-By: Steven G. Kargl <kargl@gcc.gnu.org>
(cherry picked from commit 56f03cd12be26828788a27f6f3c250041a958e45)
next prev parent reply other threads:[~2020-05-27 19:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 12:42 [Bug fortran/95104] New: " longb at cray dot com
2020-05-13 12:43 ` [Bug fortran/95104] " longb at cray dot com
2020-05-13 16:14 ` kargl at gcc dot gnu.org
2020-05-13 16:18 ` longb at cray dot com
2020-05-13 16:24 ` kargl at gcc dot gnu.org
2020-05-13 16:24 ` kargl at gcc dot gnu.org
2020-05-26 20:06 ` [Bug libfortran/95104] [9/10/11 Regression] " anlauf at gcc dot gnu.org
2020-05-26 20:30 ` anlauf at gcc dot gnu.org
2020-05-26 21:10 ` sgk at troutmask dot apl.washington.edu
2020-05-26 21:30 ` cvs-commit at gcc dot gnu.org
2020-05-26 21:34 ` [Bug libfortran/95104] [9/10 " anlauf at gcc dot gnu.org
2020-05-27 19:05 ` cvs-commit at gcc dot gnu.org
2020-05-27 19:08 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-27 19:18 ` anlauf at gcc dot gnu.org
2020-05-28 8:34 ` ro at gcc dot gnu.org
2020-05-28 19:53 ` cvs-commit at gcc dot gnu.org
2020-05-28 20:04 ` cvs-commit at gcc dot gnu.org
2020-05-28 20:14 ` cvs-commit at gcc dot gnu.org
2020-05-28 20:16 ` anlauf at gcc dot gnu.org
2020-10-18 20:47 ` longb at cray dot com
2020-10-19 5:36 ` tkoenig at gcc dot gnu.org
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=bug-95104-4-kFAfLvxmyr@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).