GC failure w/ THREAD_LOCAL_ALLOC ?

[Boehm, Hans]

GC_greatest_plausible_heap_addr is a very rough upper bound on the heap.
There will normally be unmapped addresses between it and the heap.  It's
used primarily for black-lisitng.  If we see something within the extreme
bounds but not on a proper heap page, we keep track that that page is likely
to contains a false reference.

If you see another crash/hang, it's useful to call GC_dump() from the
debugger.  That also dumps the root segments as well as some other stuff.

Hans

-----Original Message-----
From: Jeff Sturm
...

On further inspection the problem I reported has probably has nothing to
do with THREAD_LOCAL_ALLOC.  I'm still looking at it.
GC_greatest_plausible_heap_addr looks suspicious though... is there
supposed to be any assurance addresses below this are mapped?

Jeff