This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cpp memory corruption in gcc 3.3

From: "Zack Weinberg" <zack at codesourcery dot com>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 23 Oct 2003 22:59:37 -0700
Subject: Re: Cpp memory corruption in gcc 3.3
References: <20031023195937.GA10911@lucon.org><87vfqfekbe.fsf@egil.codesourcery.com><20031023233845.GB14465@lucon.org>

"H. J. Lu" <hjl@lucon.org> writes:

> There are so many files involved. However this patch seems to work
> for me on my testcase. The problem is pfile->cur_token was advanced
> beyond what was returned by alloc_expansion_token. Does that make any
> senses?  

Test.  Case.

zw

Follow-Ups:
- Re: Cpp memory corruption in gcc 3.3
  - From: H. J. Lu

References:
- Cpp memory corruption in gcc 3.3
  - From: H. J. Lu
- Re: Cpp memory corruption in gcc 3.3
  - From: Zack Weinberg
- Re: Cpp memory corruption in gcc 3.3
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]