public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56816] ICE in delete_root
Date: Wed, 03 Apr 2013 19:36:00 -0000	[thread overview]
Message-ID: <bug-56816-4-N3apb1SOKR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56816-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56816

--- Comment #6 from Mikael Morin <mikael at gcc dot gnu.org> 2013-04-03 19:36:03 UTC ---
gfc_match_select_type creates a new namespace before proceeding with parsing,
which it deletes on match failure.  However, symbols (from that namespace) that
may have been created in between are still reachable through the list of
symbols to undo (named gfc_undo_symbols previously, now
latest_undo_chgset->syms).  As the match fails, that list is used to free
(again) the symbols.

I suspect r192094 as the culprit, because it's where the gfc_match_select_type
namespace cleanup code was introduced.


  parent reply	other threads:[~2013-04-03 19:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 17:48 [Bug fortran/56816] New: f951.exe internal compiler error. segmentation fault dominique.pelletier at polymtl dot ca
2013-04-02 17:49 ` [Bug fortran/56816] " dominique.pelletier at polymtl dot ca
2013-04-02 17:59 ` Joost.VandeVondele at mat dot ethz.ch
2013-04-02 19:02 ` dominique.pelletier at polymtl dot ca
2013-04-02 19:02 ` dominique.pelletier at polymtl dot ca
2013-04-02 20:41 ` [Bug fortran/56816] ICE in delete_root tkoenig at gcc dot gnu.org
2013-04-03 19:36 ` mikael at gcc dot gnu.org [this message]
2013-04-03 20:34 ` mikael at gcc dot gnu.org
2013-04-03 20:58 ` mikael at gcc dot gnu.org
2013-04-07 11:28 ` mikael at gcc dot gnu.org
2013-04-07 11:30 ` mikael at gcc dot gnu.org
2013-04-15 12:59 ` burnus at gcc dot gnu.org
2013-04-18 18:22 ` [Bug fortran/56816] [4.8/4.9 regression] " mikael at gcc dot gnu.org
2013-04-18 18:23 ` mikael 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-56816-4-N3apb1SOKR@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).