我有两个关于boehm-gc的问题。
PS。我找不到boehm-gc的参考资料..。你能告诉我推荐信在哪里吗?
发布于 2013-12-22 07:33:48
如果您需要比gc.h头文件中提供的引用更多的引用,那么在进一步研究之前,您可能应该阅读垃圾收集器。
如果您有疑问,gc.h头就有您需要的内容:
typedef void (*GC_finalization_proc)
GC_PROTO((GC_PTR obj, GC_PTR client_data));
GC_API void GC_register_finalizer
GC_PROTO((GC_PTR obj, GC_finalization_proc fn, GC_PTR cd,
GC_finalization_proc *ofn, GC_PTR *ocd));
GC_API void GC_debug_register_finalizer
GC_PROTO((GC_PTR obj, GC_finalization_proc fn, GC_PTR cd,
GC_finalization_proc *ofn, GC_PTR *ocd));
/* When obj is no longer accessible, invoke */
/* (*fn)(obj, cd). If a and b are inaccessible, and */
/* a points to b (after disappearing links have been */
/* made to disappear), then only a will be */
/* finalized. (If this does not create any new */
/* pointers to b, then b will be finalized after the */
/* next collection.) Any finalizable object that */
/* is reachable from itself by following one or more */
/* pointers will not be finalized (or collected). */
/* Thus cycles involving finalizable objects should */
/* be avoided, or broken by disappearing links. */
/* All but the last finalizer registered for an object */
/* is ignored. */
/* Finalization may be removed by passing 0 as fn. */
/* Finalizers are implicitly unregistered just before */
/* they are invoked. */
/* The old finalizer and client data are stored in */
/* *ofn and *ocd. */
/* Fn is never invoked on an accessible object, */
/* provided hidden pointers are converted to real */
/* pointers only if the allocation lock is held, and */
/* such conversions are not performed by finalization */
/* routines. */
/* If GC_register_finalizer is aborted as a result of */
/* a signal, the object may be left with no */
/* finalization, even if neither the old nor new */
/* finalizer were NULL. */
/* Obj should be the nonNULL starting address of an */
/* object allocated by GC_malloc or friends. */
/* Note that any garbage collectable object referenced */
/* by cd will be considered accessible until the */
/* finalizer is invoked. */所以你定义了一个回调:
typedef <any type at all you want passed to the callback
as data for its own use> MY_ENVIRONMENT;
void my_callback(GC_PTR void_obj, GC_PTR void_environment) {
MY_ENVIRONMENT *env = (MY_ENVIRONMENT)void_environment;
MY_OBJECT *obj = (MY_OBJECT*)void_obj;
// Do finalization here.
}创建它的环境(如果有的话;否则只需传递空):
MY_ENVIRONMENT *my_env = new MY_ENVIRONMENT;
// Initialize if necessary.然后在新分配的对象上注册它:
MY_
MY_ENVIRONMENT old_env;
GC_finalization_proc old_proc;
GC_register_finalizer(new_obj, my_callback, my_env, &old_env, &old_proc);现在,在收集此特定对象时,将使用您的环境记录调用my_callback。
至于你的第二个问题,你漏掉了重点。Boehm GC取代malloc/new和free,并管理自己的内存领域。通常情况下,它自己决定何时做一个集合。这是典型的情况下,大部分竞技场已经用尽。垃圾收集标识空闲的块,因此有资格重新分配。正如API注释明确指出的那样,您可以强制集合和强制对象,但这些对象通常不是必需的。
https://stackoverflow.com/questions/20726948
复制相似问题