public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	tuwn@gmx.net
Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
Date: Wed, 19 Dec 2001 16:20:00 -0000	[thread overview]
Message-ID: <20011220002004.23509.qmail@sources.redhat.com> (raw)

Synopsis: gcc-20011217 reads beyond EOF on cygwin

State-Changed-From-To: open->feedback
State-Changed-By: neil
State-Changed-When: Wed Dec 19 16:20:04 2001
State-Changed-Why:
    Is there any chance you could try and debug this?
    I need to know which code path is being taken inside
    read_include_file() in cppfiles.c, when it is reading in
    the file(s) that cause the problem (e.g. longlong.h).
    In particular, we need to be sure that the in-memory
    file buffer is properly NUL-terminated.
    
    If you use -v, you will see the command line used to invoke cc1; that is what you should try and debug.
    
    Thanks.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5149


             reply	other threads:[~2001-12-20  0:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 16:20 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-19  4:26 neil
2001-12-21 23:36 Zack Weinberg
2001-12-21 10:56 Neil Booth
2001-12-21  9:26 Christopher Faylor
2001-12-21  6:46 Werner Tuchan
2001-12-20 11:16 Neil Booth
2001-12-20 11:06 Zack Weinberg
2001-12-20 10:36 Neil Booth
2001-12-20  6:46 Werner Tuchan
2001-12-18  3:56 tuwn

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=20011220002004.23509.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=tuwn@gmx.net \
    /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).