Nicholas Nethercote wrote:
[snip]
> It's a simplified version of a real problem, where a user implements a
> custom allocator on top of malloc(). ...
> 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
> cho
Hi,
https://bugs.kde.org/show_bug.cgi?id=100628 concerns a program like this:
#include
#include "valgrind.h"
int main(void)
{
char* x;
x = malloc(1000);
VALGRIND_MALLOCLIKE_BLOCK(x, /*szB*/ 16, /*rzB*/0, /*is_zeroed*/0);
VALGRIND_MALLOCLIKE_BLOCK(x+100, /*szB*/ 32, /*rzB*/0, /*
