public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "domob at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40850] double free in nested types with allocatable components Date: Fri, 12 Feb 2010 13:51:00 -0000 [thread overview] Message-ID: <20100212135117.3446.qmail@sourceware.org> (raw) In-Reply-To: <bug-40850-17129@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from domob at gcc dot gnu dot org 2010-02-12 13:51 ------- I hit this bug, too, it seems. My reduced test-case: PROGRAM analysis IMPLICIT NONE TYPE numlist REAL, ALLOCATABLE :: nums(:) END TYPE numlist TYPE(numlist) :: lines ALLOCATE (lines%nums(1)) CALL test ((/ lines /)) CONTAINS SUBROUTINE test (vec) TYPE(numlist), INTENT(IN) :: vec(:) END SUbROUTINE test END PROGRAM analysis This produces 126 lines of -fdump-tree-original, so I hope it may help here as being "simpler" than the one posted by Janus (it seems). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40850
next prev parent reply other threads:[~2010-02-12 13:51 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-24 19:35 [Bug fortran/40850] New: "double free or corruption" returning derived " mrestelli at gmail dot com 2009-07-25 7:33 ` [Bug fortran/40850] " burnus at gcc dot gnu dot org 2009-11-27 14:28 ` mrestelli at gmail dot com 2009-11-27 14:45 ` mrestelli at gmail dot com 2009-12-06 18:15 ` [Bug fortran/40850] double free in nested " dfranke at gcc dot gnu dot org 2009-12-07 21:01 ` janus at gcc dot gnu dot org 2010-01-07 14:49 ` pault at gcc dot gnu dot org 2010-01-29 18:24 ` mrestelli at gmail dot com 2010-02-12 13:51 ` domob at gcc dot gnu dot org [this message] 2010-03-07 17:24 ` dominiq at lps dot ens dot fr [not found] <bug-40850-4@http.gcc.gnu.org/bugzilla/> 2010-12-28 22:56 ` dfranke at gcc dot gnu.org 2011-02-21 7:56 ` burnus at gcc dot gnu.org 2011-02-21 13:02 ` mikael at gcc dot gnu.org 2011-02-21 13:04 ` mikael at gcc dot gnu.org 2011-02-23 23:08 ` mikael at gcc dot gnu.org 2012-04-26 14:04 ` janus at gcc dot gnu.org 2012-06-06 20:20 ` b.w.barker at gmail dot com 2012-06-06 20:58 ` janus at gcc dot gnu.org 2012-06-09 22:49 ` b.w.barker at gmail dot com 2012-10-06 21:26 ` 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=20100212135117.3446.qmail@sourceware.org \ --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: linkBe 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).