From: Bernhard Heckel <bernhard.heckel@intel.com>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
"bernhard.heckel" <bernhard.heckel@intel.com>
Subject: [PATCH] testsuite: Nullify pointers before first usage.
Date: Mon, 22 Feb 2016 14:50:00 -0000 [thread overview]
Message-ID: <1456152558-3962-2-git-send-email-bernhard.heckel@intel.com> (raw)
In-Reply-To: <1456152558-3962-1-git-send-email-bernhard.heckel@intel.com>
From: "bernhard.heckel" <bernhard.heckel@intel.com>
Nullify pointers to avoid an undefined association status.
2016-02-18 Bernhard Heckel <bernhard.heckel@intel.com>
gdb/Changelog:
* vla.f90: Nullify pointer after declaration.
---
gdb/testsuite/gdb.mi/vla.f90 | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/testsuite/gdb.mi/vla.f90 b/gdb/testsuite/gdb.mi/vla.f90
index 10c3dcc..c3e48dc 100644
--- a/gdb/testsuite/gdb.mi/vla.f90
+++ b/gdb/testsuite/gdb.mi/vla.f90
@@ -18,6 +18,7 @@ program vla
real, target, allocatable :: vla2(:, :)
real, pointer :: pvla2 (:, :)
logical :: l
+ nullify (pvla2)
allocate (vla1 (5)) ! vla1-not-allocated
l = allocated(vla1) ! vla1-allocated
--
2.7.1.339.g0233b80
next prev parent reply other threads:[~2016-02-22 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:49 [PATCH] Fix detection of gfortran compilers Bernhard Heckel
2016-02-22 14:50 ` Bernhard Heckel [this message]
2016-02-26 16:49 ` [PATCH] testsuite: Nullify pointers before first usage Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Fix run to main issue introduced by GCC 5.x Bernhard Heckel
2016-02-26 16:55 ` Joel Brobecker
2016-03-02 15:44 ` Heckel, Bernhard
2016-02-22 14:50 ` [PATCH] testsuite: Fix timeout issues during print of vla-arrays Bernhard Heckel
2016-02-23 19:37 ` Luis Machado
2016-02-24 8:03 ` Heckel, Bernhard
2016-02-24 14:47 ` Yao Qi
2016-02-25 13:16 ` Heckel, Bernhard
2016-02-26 16:47 ` [PATCH] Fix detection of gfortran compilers Joel Brobecker
2016-03-02 15:45 ` Heckel, Bernhard
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=1456152558-3962-2-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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