Re[2]: [Gc]: Re: Partially scanning a VM's call stack

Ivan Maidanski ivmai at
Fri Aug 28 10:05:15 PDT 2009


"Boehm, Hans" <hans.boehm at> wrote:
> > ...
> >   GC_init_gcj_malloc(5, 0); /* magical 5 for mp=0 (as used in 
> > other projects on the web) */
> This is definitely intended to be part of the public interface.
> The GC_init_gcj_malloc interface could be a bit better documented.
> The technical problem is that it should logically rely in GC_new_proc,
> but can't, since for something like JVM or Mono, the compiler
> has to generate mark descriptors, and hence needs to know the mark
> proc index in advance.  I'll improve the comment a bit.
> (Passing a null mark proc at least breaks the debugging interface,
> and is not recommended.  Any small integer will probably work for the
> index.)

I don't use GC_DS_PROC and I don't want to pass a fake proc to it (but I do want to stay within the GCJ API). It's unclear (to me) how should GC_gcj_debug_kind be correctly initialized if the client doesn't use mp at all (but may happen to call GC_debug_gcj_malloc()). Could you point me?


More information about the Gc mailing list