public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/62043] [4.9/4.10 Regression] GCC hangs / aborts / double free or corruption (!prev) on invalid input
Date: Thu, 07 Aug 2014 19:49:00 -0000	[thread overview]
Message-ID: <bug-62043-4-Rk9Quufb0n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62043-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Thu Aug  7 19:48:36 2014
New Revision: 213732

URL: https://gcc.gnu.org/viewcvs?rev=213732&root=gcc&view=rev
Log:
    PR c++/62043
    * parser.c (c_parse_file): Change sorry to fatal_error.

Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c


  parent reply	other threads:[~2014-08-07 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07  1:45 [Bug c++/62043] New: " d.g.gorbachev at gmail dot com
2014-08-07  1:47 ` [Bug c++/62043] " d.g.gorbachev at gmail dot com
2014-08-07  2:36 ` pinskia at gcc dot gnu.org
2014-08-07  9:38 ` rguenth at gcc dot gnu.org
2014-08-07 19:49 ` jason at gcc dot gnu.org [this message]
2014-08-07 19:50 ` jason 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-62043-4-Rk9Quufb0n@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).