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/54784] [OOP] allocation of extended types with polymorphic allocatable members
Date: Tue, 02 Oct 2012 21:52:00 -0000 [thread overview]
Message-ID: <bug-54784-4-RfVhXoVGPB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54784-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54784
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Keywords| |wrong-code
Last reconfirmed| |2012-10-02
CC| |janus at gcc dot gnu.org
Ever Confirmed|0 |1
Summary|[oop] allocation of |[OOP] allocation of
|extended types with |extended types with
|polymorphic allocatable |polymorphic allocatable
|members |members
--- Comment #1 from janus at gcc dot gnu.org 2012-10-02 21:51:49 UTC ---
Thanks for reporting this. I can reproduce it with 4.7 and trunk. Here is a
reduced test case:
program bug
implicit none
type :: block
real, allocatable :: fields
end type
type :: list
class(block),allocatable :: B
end type
type :: domain
type(list),dimension(2) :: L
end type
type(domain) :: d
type(block) :: b1
allocate(d%L(2)%B,source=b1)
end program bug
This fails at runtime with:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7F379D1FDA97
#1 0x7F379D1FE074
#2 0x7F379C72ED9F
#3 0x400804 in __copy_bug_Block at bug.f90:9
#4 0x40097C in bug at bug.f90:19 (discriminator 2)
Segmentation fault
valgrind shows:
==11046== Invalid read of size 8
==11046== at 0x400804: __copy_bug_Block (bug.f90:9)
==11046== by 0x40097C: MAIN__ (bug.f90:19)
==11046== by 0x400A88: main (bug.f90:21)
==11046== Address 0x0 is not stack'd, malloc'd or (recently) free'd
next prev parent reply other threads:[~2012-10-02 21:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 20:07 [Bug fortran/54784] New: [oop] " jkozdon at gmail dot com
2012-10-02 21:52 ` janus at gcc dot gnu.org [this message]
2012-10-02 22:15 ` [Bug fortran/54784] [OOP] " jkozdon at gmail dot com
2012-10-02 22:36 ` janus at gcc dot gnu.org
2012-10-02 22:46 ` janus at gcc dot gnu.org
2012-10-02 23:44 ` janus at gcc dot gnu.org
2012-10-03 10:38 ` janus at gcc dot gnu.org
2012-10-03 16:09 ` [Bug fortran/54784] [4.7/4.8 Regression] [OOP] wrong code in polymorphic allocation with SOURCE janus at gcc dot gnu.org
2012-10-08 16:23 ` sfilippone at uniroma2 dot it
2012-10-09 10:00 ` sfilippone at uniroma2 dot it
2012-10-10 11:49 ` janus at gcc dot gnu.org
2012-10-11 17:53 ` janus at gcc dot gnu.org
2012-10-11 17:58 ` janus at gcc dot gnu.org
2012-10-14 22:16 ` janus at gcc dot gnu.org
2012-10-14 22:27 ` janus 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-54784-4-RfVhXoVGPB@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).