--pEAjBjStGYT6H+Py
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 23, 2006 at 07:34:14AM +0100, David Malone wrote:
> > I presume this surrounds each allocation with extra padding filled
> > with known content, and checks that the padding is undisturbed later?
> > That more general solution sounds very useful too; I'm not sure if we
> > have something like this, but we probably should.
>=20
> It actually puts each allocation in its own page. When the allocation
> is freed the vm system sets up the page to cause a fault if the
> page is accessed. That way we can catch code that uses-after-free.

Ah. Coverity has helped in this area, but even so both ideas sound
like they could be of value. Any volunteers? :)

> It's very wasteful of memory, but is only intended as a debugging tool.

I bet :)

> (At the moment you attach the option to a particular allocation type.)

I imagine we'd set it as a per-pool flag, pretty much the same thing.

--
Dan.
--pEAjBjStGYT6H+Py
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (NetBSD)

iD8DBQFE7p3uEAVxvV4N66cRAvuvAKDytJGbQ48U9mdS+zJ3APA/eNFppACg7eoz
/9O1Pz9tGgURdkw5l2bzOuo=
=/uQD
-----END PGP SIGNATURE-----

--pEAjBjStGYT6H+Py--