On Dec 20, 8:32 pm, Dan Grayson wrote:
> I don't see how your "make check" routine could ever even come into
> contact with my custom allocator. Also, it's probably not worth your
> while to try to distinguish a custom allocator from your native
> allocator at run time, as it will waste time.
>
2009/12/20 Dan Grayson :
> I don't see how your "make check" routine could ever even come into
> contact with my custom allocator.
True.
> Also, it's probably not worth your
> while to try to distinguish a custom allocator from your native
> allocator at run time, as it will waste time.
Agreed.
I don't see how your "make check" routine could ever even come into
contact with my custom allocator. Also, it's probably not worth your
while to try to distinguish a custom allocator from your native
allocator at run time, as it will waste time.
I suggest checking every pointer returned by the a
