public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64230] [4.9/5 Regression] Segmentation fault - invalid memory reference in a compiler-generated finalizer for a complicated type hierarchy when a polymorphic variable is allocated in an external procedure.
Date: Mon, 08 Dec 2014 21:45:00 -0000	[thread overview]
Message-ID: <bug-64230-4-5jeCwQgX0e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64230-4@http.gcc.gnu.org/bugzilla/>

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

Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-12-08
                 CC|                            |Joost.VandeVondele at mat dot ethz
                   |                            |.ch
      Known to work|                            |4.8.3
   Target Milestone|---                         |4.9.3
            Summary|Segmentation fault -        |[4.9/5 Regression]
                   |invalid memory reference in |Segmentation fault -
                   |a compiler-generated        |invalid memory reference in
                   |finalizer for a complicated |a compiler-generated
                   |type hierarchy when a       |finalizer for a complicated
                   |polymorphic variable is     |type hierarchy when a
                   |allocated in an external    |polymorphic variable is
                   |procedure.                  |allocated in an external
                   |                            |procedure.
     Ever confirmed|0                           |1
      Known to fail|                            |4.9.2, 5.0

--- Comment #1 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
yes, confirmed, also with trunk (and -fsanitize=undefined)

> gfortran -g -fno-omit-frame-pointer -fsanitize=undefined t.f90 && ./a.out
t.f90:24: runtime error: member access within null pointer of type 'struct t6'


       reply	other threads:[~2014-12-08 21:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-64230-4@http.gcc.gnu.org/bugzilla/>
2014-12-08 21:45 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2014-12-09 12:38 ` rguenth at gcc dot gnu.org
2014-12-15 19:12 ` janus at gcc dot gnu.org
2015-01-19 14:10 ` janus at gcc dot gnu.org
2015-01-26 15:57 ` [Bug fortran/64230] [4.9/5 Regression] Invalid memory reference in a compiler-generated finalizer for allocatable component janus at gcc dot gnu.org
2015-01-26 18:54 ` janus at gcc dot gnu.org
2015-01-26 18:55 ` janus at gcc dot gnu.org
2015-01-27 18:37 ` janus at gcc dot gnu.org
2015-01-27 19:50 ` janus at gcc dot gnu.org
2015-04-24 12:39 ` mathewc at nag dot co.uk
2015-04-25  7:49 ` dominiq at lps dot ens.fr
2015-04-27  6:45 ` mathewc at nag dot co.uk

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-64230-4-5jeCwQgX0e@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).