public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: giovannibajo at libero dot it <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org, per@bothner.com
Subject: Re: [Bug preprocessor/11361] New: [3.4 regression] ICE (segfault) in c-lex.c with one-liner
Date: Sat, 28 Jun 2003 20:06:00 -0000	[thread overview]
Message-ID: <20030628200639.GA3106@daikokuya.co.uk> (raw)
In-Reply-To: <20030628161840.11361.giovannibajo@libero.it>

giovannibajo at libero dot it wrote:-

> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11361
> 
>            Summary: [3.4 regression] ICE (segfault) in c-lex.c with one-
>                     liner
>            Product: gcc
>            Version: 3.4
>             Status: UNCONFIRMED
>           Keywords: ice-on-invalid-code
>           Severity: normal
>           Priority: P2
>          Component: preprocessor
>         AssignedTo: unassigned at gcc dot gnu dot org
>         ReportedBy: giovannibajo at libero dot it
>                 CC: gcc-bugs at gcc dot gnu dot org
>  GCC build triplet: i686-pc-cygwin
>   GCC host triplet: i686-pc-cygwin
> GCC target triplet: i686-pc-cygwin
> 
> Just compile this line:
> 
> # 31 "eval.c" 2
> 
> to get a segmentation fault.

Per, this was introduced by your line-map.c change of a few months ago.
line-map.c used to guarantee to retain internal consistency even if
the client gave it nonsense, and cpplib relies on that.  After your
patch, it no longer maintains internal consistency.

Neil.


  parent reply	other threads:[~2003-06-28 20:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28 16:18 giovannibajo at libero dot it
2003-06-28 16:28 ` [Bug preprocessor/11361] " pinskia at physics dot uc dot edu
2003-06-28 20:06 ` Neil Booth [this message]
2003-06-28 20:06 ` neil at daikokuya dot co dot uk
2003-06-28 20:14 ` giovannibajo at libero dot it
2003-07-15 15:21 ` pinskia at physics dot uc dot edu
2003-07-22 23:11 ` cvs-commit at gcc dot gnu dot org
2003-07-22 23:16 ` pinskia at physics dot uc dot edu

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=20030628200639.GA3106@daikokuya.co.uk \
    --to=neil@daikokuya.co.uk \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@gcc.gnu.org \
    --cc=per@bothner.com \
    /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).