This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: GC failure w/ THREAD_LOCAL_ALLOC ?
- From: Jeff Sturm <jsturm at one-point dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Bryce McKinlay '" <bryce at waitaki dot otago dot ac dot nz>, "''Michael Smith' '" <msmith at spinnakernet dot com>, "''java at gcc dot gnu dot org' '" <java at gcc dot gnu dot org>
- Date: Thu, 21 Mar 2002 12:59:38 -0500 (EST)
- Subject: RE: GC failure w/ THREAD_LOCAL_ALLOC ?
On Wed, 20 Mar 2002, Boehm, Hans wrote:
> GC_greatest_plausible_heap_addr is a very rough upper bound on the heap.
OK, I was wondering because in my case it's awfully far from the
heap, there's something like a 40MB hole in between the highest heap
address and GC_greatest_plausible_heap_addr.
> 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.
I can do that again. For now I've rebuilt libgcj with conservative
marking (no descriptors), and the failure I reported has vanished.
When marking from a descriptor, what tests are done to ensure a pointer is
within heap boundaries?
Jeff