From:	GAMMELJL AT SLU DOT EDU
Date:	Mon, 27 Sep 1999 14:07:28 -0500 (CDT)
Subject:	Re: problem with malloc.c attn: Michael Bukin and Eli Zaretskii
To:	djgpp AT delorie DOT com
Message-id:	<01JGGU5V1COM8WW5WR@SLU.EDU>
Organization:	SAINT LOUIS UNIVERSITY St. Louis, MO
X-VMS-To:	IN%"djgpp AT delorie DOT com"
MIME-version:	1.0
Reply-To:	djgpp AT delorie DOT com

     There is no doubt tht Michael Bukin is exactly on target.  If I
define zvector gg; and write
          g=e+f;
          ....print g...
          gg=f+e;
          ...print gg...
I have no trouble at all.  Using g in the last two lines results in the
error screens which occur after all the computing and printing have been
done correctly, that is when exiting main().  There is no doubt that
an effort is being made to free (or delete) g twice when g is used
in the last two lines.
     The problem is: what to do about this.  It is an absurd situation.
Other compilers, such as the Watcom C/C++ compiler, and indeed the
Delorie port of the gnu compiler with the old malloc.c, have no trouble.
Why should the Delorie port of the gnu compiler with the new malloc.c?
Come on!                            
     Of course,  I deeply appreciate your attention to my problems and
highly value the Delorie products and team which does the work.
     Thanks and best wishes.

- Raw text -