GC failure w/ THREAD_LOCAL_ALLOC ?

Wed Mar 20 12:13:00 GMT 2002

On 2002年3月20日, Bryce McKinlay wrote:
> It runs fine without THREAD_LOCAL_ALLOC.

You're having better luck than I am, then. I did get random, infrequent
crashes in my application. But without THREAD_LOCAL_ALLOC I don't get
that far:
0x40c45363 in GC_mark_from (mark_stack_top=0x805b0e8,
mark_stack=0x805b000,
 mark_stack_limit=0x8063000) at ../../../boehm-gc/mark.c:654
654 deferred = *limit;
(gdb) p limit
1ドル = (word *) 0x86e90c4
the address isn't mapped:
(gdb) call GC_print_heap_sects()
Total heap size: 5672960
Section 0 from 0x806b000 to 0x807b000 2/16 blacklisted
Section 1 from 0x808b000 to 0x809b000 0/16 blacklisted
Section 2 from 0x809d000 to 0x80ad000 0/16 blacklisted
Section 3 from 0x80ad000 to 0x80be000 0/17 blacklisted
Section 4 from 0x80d9000 to 0x80f3000 0/26 blacklisted
Section 5 from 0x80f3000 to 0x8112000 0/31 blacklisted
Section 6 from 0x8131000 to 0x815a000 0/41 blacklisted
Section 7 from 0x815a000 to 0x8191000 0/55 blacklisted
Section 8 from 0x8191000 to 0x81fe000 0/109 blacklisted
Section 9 from 0x8268000 to 0x82d6000 0/110 blacklisted
Section 10 from 0x82f4000 to 0x8386000 1/146 blacklisted
Section 11 from 0x8386000 to 0x8449000 1/195 blacklisted
Section 12 from 0x8459000 to 0x855d000 0/260 blacklisted
Section 13 from 0x857e000 to 0x86d9000 15/347 blacklisted
(gdb) p GC_greatest_plausible_heap_addr
2ドル = 0xaed9000
I give up for now, other than to note that 3.1 isn't ready, at least for
my uses. I can still use 3.0.
Jeff