--verify-predictable mode added for ensuring that GC behaves deterministically.

src/spaces.cc

Index: src/spaces.cc
diff --git a/src/spaces.cc b/src/spaces.cc
index 7966a04728c6291e83142eeeda1acf2039c68c77..6ac40a9899be8561c6413c6221c04fea31260ec3 100644
--- a/src/spaces.cc
+++ b/src/spaces.cc
@@ -2897,6 +2897,9 @@ AllocationResult LargeObjectSpace::AllocateRaw(int object_size,
   }
 
   heap()->incremental_marking()->OldSpaceStep(object_size);
+  if (FLAG_allocations_digest) {
+    heap()->OnAllocationEvent(object, object_size);

[Hannes Payer (out of office), 2014/06/09 15:23:51]

The event call should be in Heap::AllocateRaw. There is actually already a call
to profiler->AllocationEvent. This is catching the same event for a different
purpose. I guess we can refactor there.

[Igor Sheludko, 2014/06/10 08:22:54]

I trigger "allocation event" each time any allocation happens (either object or
target place for evacuation), while profiler has to distinguish between new
object creation and object relocation. I think that for this verification
purpose we can keep things simple. WDYT?

[Hannes Payer (out of office), 2014/06/10 16:58:59]

1) Please move your monitoring code into Heap:AllocateRaw. That is our runtime
allocation choke point.
2) I would assume that it your monitoring call will be at the exact same
location as profiler->AllocationEvent. Hence, re-using this infrastructure would
keep stuff simple.
WDYT?

+  }
   return object;
 }