Laurynas Biveinis wrote: > 2006/6/18, Daniel Berlin <[EMAIL PROTECTED]>: >> Are you trying to do incremental marking? >> If the root set changes in the middle of an incremental mark and it's >> still got things from the old root set to mark, i bet it blows up, :) > > I thought I was safe with disabled incremental collection. > Additionally http://gcc.gnu.org/ml/java/2005-12/msg00059.html and > other messages I was able to find mention incremental marking only in > context of of incremental collection, leaving me to guess that it is > not a part of full collection. Moreover I have GC disabled most of the > time (enabling just for ggc_collect()), that might disable marking at > allocation if it existed (a guess, I know...) > > All in all, I'm not sure incremental marking is at fault here.
Okay, i'm just saying it looks like it's trying to mark a range that has moved. You should probably copy Hans, or email the gc list, and see if they have any idea. You can probably also get it to crash much quicker if you use --param ggc-min-heapsize=0 --ggc-min-expand=0 (assuming you are still using the heuristics inside ggc_collect), which will cause it to collect at every call.
