public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60357] [F08] structure constructor with unspecified values for allocatable components
Date: Tue, 23 Dec 2014 23:46:00 -0000	[thread overview]
Message-ID: <bug-60357-4-47PQgWZusR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60357-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60357

--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #4)
>     program testerprog
>     use testmod
>     Type(A) :: Me
>     allocate(Me%y)
>     Me = A(X=1, y=2)
>     print *, Me%y
> 
>     end program
> 
> gives
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.

Confirmed. However, this segfault is not related to the original bug (nor to
the patch I posted). It's a separate issue.


  parent reply	other threads:[~2014-12-23 23:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 14:56 [Bug fortran/60357] New: " antony at cosmologist dot info
2014-02-27 22:19 ` [Bug fortran/60357] [F08] " janus at gcc dot gnu.org
2014-02-28 17:35 ` janus at gcc dot gnu.org
2014-08-12 15:15 ` dominiq at lps dot ens.fr
2014-12-21 14:14 ` dominiq at lps dot ens.fr
2014-12-23 23:46 ` janus at gcc dot gnu.org [this message]
2014-12-29 10:46 ` janus at gcc dot gnu.org
2014-12-29 10:55 ` janus at gcc dot gnu.org
2014-12-29 14:59 ` vehre at gmx dot de
2014-12-29 16:42 ` janus at gcc dot gnu.org
2014-12-29 17:37 ` vehre at gmx dot de
2014-12-29 17:37 ` vehre at gmx dot de
2015-01-17 18:09 ` pault at gcc dot gnu.org
2015-01-26 10:57 ` vehre 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-60357-4-47PQgWZusR@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).