This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
- From: neil at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tuwn at gmx dot net
- Date: 20 Dec 2001 00:20:04 -0000
- Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
- Reply-to: neil at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tuwn at gmx dot net, gcc-gnats at gcc dot gnu dot org
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