Mail Archives: djgpp-workers/2004/12/09/07:36:42
Esa A E Peuha wrote:
> 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.
What is YAMD?
>
>> 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.
Where can I find the "current memalign", which I assume is working
with nmalloc. Can I assume my malldbg module is also incorporated
already (it is in the nmalloc package). I assume that the
installed nmalloc is my code unchanged apart from stripping the
unfinished memalign code.
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!
- Raw text -