Re: GC leaks debugging

On 05/04/11 05:41, Boehm, Hans wrote:

> I'm still concerned about the amount of blacklisting here.  Can you
> track down some of those messages or calls to
> GC_add_to_black_list_normal, and find out where those bogus
> pointer-like bit patterns are coming from?
> 
> Is there any way to get the reflection information (and exception
> information? or was that fixed?) into read-only segments, so that
> the collector can know not to scan them?

It's not easy.  That's already been done with indirect dispatch, but
it doesn't work with the core library.  The easiest way to get it
working for all classes may be to get CNI working wthe indirect
dispatch.

Andrew.