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/64397] [OOP] Runtime segfault with parenthesis expression passed to polymorphic dummy argument
Date: Tue, 23 Dec 2014 22:59:00 -0000 [thread overview]
Message-ID: <bug-64397-4-prhmNxoeTF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64397-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to patnel97269-gfortran from comment #5)
> I agree that this example still trigger a bug, but I remember in my original
> (more complicated) code, the segfault appears when it tries to access the
> allocatable components of the type in the subroutine
Are you sure? In my debugging sessions, it always seemed like the segfault
happened after the subroutine call.
next prev parent reply other threads:[~2014-12-23 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64397-4@http.gcc.gnu.org/bugzilla/>
2014-12-23 21:52 ` [Bug fortran/64397] [OOP] Runtime segfault with type-bound assignment and parenthesis janus at gcc dot gnu.org
2014-12-23 22:10 ` dominiq at lps dot ens.fr
2014-12-23 22:19 ` janus at gcc dot gnu.org
2014-12-23 22:27 ` [Bug fortran/64397] [OOP] Runtime segfault with parenthesis expression passed to polymorphic dummy argument janus at gcc dot gnu.org
2014-12-23 22:44 ` patnel97269-gfortran at yahoo dot fr
2014-12-23 22:59 ` janus at gcc dot gnu.org [this message]
2014-12-23 23:19 ` patnel97269-gfortran at yahoo dot fr
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-64397-4-prhmNxoeTF@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).