boehm-gc

I've read article in LinuxJournal about Boehm-Demers-Weiser garbage collector library . I'm interesting to use it in my library instead of my own reference counting implementation. I have only one question: is it possible to use gc only for my shared library and still use malloc/free in the main application? I'm not quite understand how gc checks the heap so I'm worrying about performance of gc in that case and possible side effects. The example in the manual states: It is usually best not to mix garbage-collected allocation with the system malloc - free . If you do, you need to be careful not

I stumbled about this question: Button in ContentView causes crash in MonoTouch runtime. Bug in Monotouch 4.0? and the inquirer has problems with Monotouch's "more aggressive" garbage collector. Can somebody explain why in the inquirer's case the error is issued (what gets collected and why?)? What does "more aggressive" mean? What are the traps I can fall into? What should I avoid? With regards to iOS5: Apple claims with iOS5 the app will get one memory warning and then it will get killed. Unlike any other version before, where an app received three warnings. What does that mean for Monotouch

The Boehm's conservative garbage collector is quite useful (e.g. Bigloo is using it, Guile is using something similar, etc....), notably on Linux (which is the only OS I care about; I'm using Debian/Sid/x86-64 if that matters, and libgc-dev package is version 1:7.4.2-8 so the Boehm GC is 7.4.2). However, Boehm's GC requires to be aware of every thread using it. Its gc_pthreads_redirects.h (more or less internal) header file is redefining pthread_create as # define pthread_create GC_pthread_create Actually, what Boehm's GC needs is GC_register_my_thread to be called early in the new thread call