This is the mail archive of the
mailing list for the GCC project.
Re: attempt to use poisoned "malloc"?
- From: Eric Christopher <echristo at redhat dot com>
- To: Steven Z <GccList at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 15 Sep 2004 11:52:32 -0700
- Subject: Re: attempt to use poisoned "malloc"?
- References: <email@example.com>
On Wed, 2004-09-15 at 09:15, Steven Z wrote:
> Hi, there:
> I used to work on changing gcc-3.3 with compiler gcc-2.97. My system
> crashed and I reinstalled RedHat FC2. The default compiler on FC2 is
> gcc-3.3.3. Then the used-to-work codes generates error like:
> attempt to use poisoned "malloc"
> I tried to change malloc to calloc. That makes no difference other
> than generating error message like:
> attempt to use poisoned "calloc"
> Does anyone have any idea on why this error is generated? What is
> possible solution? Does this have anything to do with different
> versions of gcc?
It's likely the version of bison that is in FC2. You may wish to try
using the YYMALLOC patch that's in the source to gcc in FC2.
IIRC the line was something like:
#define YYMALLOC nonexistent
that would go in c-parse.in, tradcif.y and cp/parse.y.
Eric Christopher <firstname.lastname@example.org>