X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Date:	Thu, 9 Dec 2004 13:03:12 +0200 (EET)
From:	Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Sender:	peuha AT sirppi DOT helsinki DOT fi
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Bison 1.875 (release 2)
In-Reply-To:	<41B77385.44C11362@yahoo.com>
Message-ID:	<Pine.OSF.4.58.0412091253210.22467@sirppi.helsinki.fi>
References:	<41B7381F DOT 20566 DOT E3E148 AT localhost> <41B77385 DOT 44C11362 AT yahoo DOT com>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 8 Dec 2004, CBFalconer wrote:

> Juan Manuel Guerrero wrote:

> > The reason for
> > the bison failure was that I allocated an string using strlen()
> > without adding one byte more for the terminating '\0'. Later when
> > this string was free()ed with djdev204 the program crashed. But
> > free() of djdev203 never complained abuot this so I never noticed
> > this bug.

That's why it would be good to test programs with YAMD; it catches any
overrun of malloced buffers reliably.

> Does this mean that my nmalloc is now incorporated in 2.04?

I think so.  The malloc of 2.03 is buggy, and the earlier malloc from
BSD wasn't very good either, so clearly nmalloc is the best we've got.

> I know I promised to finish the memalign alteration, and I did
> start it, but I have just returned from the hospital with a triple
> bypass.

I'm sorry to hear that.  Hope you get well soon.

> At any rate, I have done no more work on memalign, and
> probably won't for at least the next month.

In that case we probably should release 2.04 with the current memalign.
It seems to be quite reliable after fixing the bugs I reported months
ago.

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/

- Raw text -