如何为 Splint 注释 BoehmGC 收集的代码？
Splint 可以很好地追踪 C 代码中的内存泄漏。每个malloc() 都应该有一个匹配的free()。但 BoehmGC 收集的代码使用 GC_MALLOC() 且没有匹配的 GC_FREE()。这使得 Splint 因大量实际上并不存在的内存泄漏消息而变得疯狂。
有谁知道此类代码的正确注释，以便 Splint 不再显示虚假的内存泄漏消息？
特别是，有人可以注释 维基百科 BoehmGC 示例吗？
#include <assert.h>
#include <stdio.h>
#include <gc.h>
int main(void)
{
int i;
GC_INIT();
for (i = 0; i < 10000000; ++i)
{
int **p = GC_MALLOC(sizeof(int *));
int *q = GC_MALLOC_ATOMIC(sizeof(int));
assert(*p == 0);
*p = GC_REALLOC(q, 2 * sizeof(int));
if (i % 100000 == 0)
printf("Heap size = %zu\n", GC_get_heap_size());
}
return 0;
}
Splint does a good job tracking down memory leaks in C code. Every malloc() should have a matching free(). But BoehmGC-collected code uses GC_MALLOC() with no matching GC_FREE(). This makes Splint go crazy with tons of messages about memory leaks that aren't actually there.
Does anyone know the proper annotation for such code so that Splint no longer shows spurious memory leak messages?
In particular, could someone annotate Wikipedia's BoehmGC example?
#include <assert.h>
#include <stdio.h>
#include <gc.h>
int main(void)
{
int i;
GC_INIT();
for (i = 0; i < 10000000; ++i)
{
int **p = GC_MALLOC(sizeof(int *));
int *q = GC_MALLOC_ATOMIC(sizeof(int));
assert(*p == 0);
*p = GC_REALLOC(q, 2 * sizeof(int));
if (i % 100000 == 0)
printf("Heap size = %zu\n", GC_get_heap_size());
}
return 0;
}
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为您应该注释BoehmGC API 本身，然后示例所需的注释（如果有）就会变得明显。
对于初学者来说，没有注释的函数返回的任何指针都是隐式
@only，这意味着您必须在引用丢失之前释放关联的内存。因此，第一步是注释分配器，以便它们不再返回@only引用。相反，手册建议使用共享引用：如果您不想修改 BoehmGC API，您可以通过创建正确注释的包装函数来解决它。此外，您需要在包装函数中禁用特定的传输错误（因为它们从 BoehmGC API 获取隐式
@only引用，然后将其返回为@共享）。例如，这是您在代码的给定点禁用“语句无效”错误的方法：
包装函数将如下所示：
然后在示例中您将使用
MY_GC_MALLOC而不是GC_MALLOC。I think that you should annotate the BoehmGC API itself, and then the annotations needed for the example (if any) will become obvious.
For starters, any pointer returned by a function with no annotation is implicitly
@only, which means that you must release the associated memory before reference is lost. Therefore, the first step would be to annotate the allocators so that they no longer return an@onlyreference. Instead, the manual advises using shared references:If you didn't want to modify the BoehmGC API, you could work around it by creating properly annotated, wrapper functions. In addition, you would need to disable specific transfer errors within your wrapper functions (because they get an implicit
@onlyreference from the BoehmGC API and then return it as@shared).For example, this is the way you would disable the "Statement has no effect" error at a given point of your code:
The wrapper function would be something like this:
Then in the example you'd use
MY_GC_MALLOCrather thanGC_MALLOC.