[Guy Harris <gharris@xxxxxxxxx>]

Gerald Combs wrote:
> I just checked in a change to emem.c that adds canary values after each
> memory allocation.

Unfortunately, it also breaks the compile with MSVC++ (it doesn't allow 
adding constants to "void *"s - that's a GCCism; I've checked in a fix), 
and warns about open() and read() - Windows doesn't have "/dev/urandom" 
(and not all UN*Xes have it, either, although all the UN*Xes in the 
buildbot might), so that code won't work in any case.