检查内存分配-Checkmemoryallocationw/ovalgrind

1  

Looks like there are two possible solutions:

看来有两种可能的解决方案:

--soname-synonyms

If your custom allocator functions are still called malloc() and free(), use the --soname-synonyms command line parameter to tell Valgrind to look for these functions in your preloaded library. It can then automatically intercept calls to these functions. Example:

如果您的自定义分配器函数仍然被称为malloc()和free()，那么使用- sonami -synonyms命令行参数告诉Valgrind在预加载库中查找这些函数。然后它可以自动拦截对这些函数的调用。例子:

--soname-synOnyms=somalloc=mymalloclib.so

See http://valgrind.org/docs/manual/manual-core.html#manual-core.rareopts for details.

有关详细信息,请参阅http://valgrind.org/docs/manual/manual-core.html manual-core.rareopts。

Client Requests

If you have a more complicated custom allocator (with an API different from malloc()/free()), you can use special "client requests" in your malloc()/free() implementation to tell Valgrind about the structure of your memory pool. See http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools for details.

如果您有一个更复杂的自定义分配器(与malloc()/free()不同的API)，您可以在您的malloc()/free()实现中使用特殊的“客户端请求”来告诉Valgrind关于内存池的结构。有关详细信息,请参阅http://valgrind.org/docs/manual/mc-manual.html mc-manual.mempools。

I haven't tested either of these solutions :-) so would be nice to hear whether it actually works for you.

我还没有测试这两种方法中的任何一种:-)所以很高兴听到它是否真的适合你。