On Sat, Jul 25, 2009 at 11:37 PM, John Reiserjrei...@bitwagon.com wrote:
I have a patch that tolerates overlaps such as these, where a custom
block falls entirely within a malloc()'d block. But there's a design
choice to be made. In such a case, what do we do with the malloc()'d
block?
On Fri, Jul 24, 2009 at 11:12 PM, Nicholas Nethercote
n.netherc...@gmail.com wrote:
https://bugs.kde.org/show_bug.cgi?id=100628 concerns a program like this:
#include stdlib.h
#include valgrind.h
int main(void)
{
char* x;
x = malloc(1000);
VALGRIND_MALLOCLIKE_BLOCK(x, /*szB*/
