Subject:	Re: malloc bug?
To:	dj AT stealth DOT ctron DOT com (DJ Delorie)
Date:	Wed, 1 Feb 1995 18:26:41 -0600 (CST)
Cc:	enrico AT max DOT tiac DOT net, djgpp AT sun DOT soe DOT clarkson DOT edu
From:	mcastle AT umr DOT edu (Mike Castle)

Amazingly enough DJ Delorie said:
> djgpp's default malloc is pretty lame about checking for corruption.
> The most common case is accessing data outside what you allocated,
> like going off the end of an array.  This causes the NEXT malloc to
> fail, in a seemingly unrelated location.

Hmm... I seem to remember that the default malloc() in DJGPP is
the freely distributable BSD version, correct?

The gnu malloc should be fairly easy to port to djgpp, I would
expect, and one could use that as a debugging version (I think
it's GPLed, though, and so for distributing binaries, one would
prolly want to use the BSD version anyway).

Has anyone done this yet?
mrc
-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle AT cs DOT umr DOT edu     and be right all the time, or not work at all
   mcastle AT umr DOT edu       and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen

- Raw text -