From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Malloc problems
Date:	18 Apr 2000 14:38:51 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<8dhs1r$qcf$1@nets3.rz.RWTH-Aachen.DE>
References:	<8074D95288C2D311AC660000F8106CC8EA7BE0 AT MSG1CHR>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 956068731 27023 137.226.32.75 (18 Apr 2000 14:38:51 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	18 Apr 2000 14:38:51 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

DAANEN Vincent <VDAANEN AT chru-lille DOT fr> wrote:
> 	Hi
> 	recently, I downloaded gcc 2.95.2 for djgpp. Some programs those
> worked fine when compiled with gcc -2.7.. or gcc 2.8..
> 	do not work now. They break in malloc functions
> 	Is there a bug in malloc of gcc 2.95.2 ?

As malloc() is provided by the DJGPP runtime library, not GCC, that
cannot possibly be the case.

Did you really update only GCC, not also the DJGPP main package,
djdev*.zip? I ask because the malloc() in recent DJGPP versions is
quite a lot more picky than the one in old DJGPP's. It exposes bugs in
programs that passed unnoticed in older versions of DJGPP.

So, all in all: the bug is most probably in your program, not in GCC.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -