Fixing a bug: summary of conflict transitions is to be paired up with a transition...

[jpf-core.git] / jpf.properties

diff --git a/jpf.properties b/jpf.properties
index 8c0270db389d12a0fa8b2f38e1f8ae983309ad6b..0dd4cae31ba9e1b9c3f49b2ef7443c7526d87fb7 100644 (file)
--- a/jpf.properties
+++ b/jpf.properties
@@ -131,6 +131,7 @@ vm.backtracker.class = gov.nasa.jpf.vm.DefaultBacktracker
 vm.serializer.class = gov.nasa.jpf.vm.serialize.CFSerializer
 #vm.serializer.class = gov.nasa.jpf.vm.serialize.AdaptiveSerializer
 #vm.serializer.class = gov.nasa.jpf.vm.serialize.FilteringSerializer
+filter.class = gov.nasa.jpf.vm.serialize.SmartThingsFilterConfiguration
 
 # the class that models static fields and classes
 vm.statics.class = gov.nasa.jpf.vm.OVStatics
@@ -252,7 +253,7 @@ vm.finalize = false
 
 # this is a preemption boundary specifying the max number of instructions after which we
 # break the current transition if there are other runnable threads
-vm.max_transition_length = 50000
+vm.max_transition_length = 2000000000
 
 # are thread ids of terminated threads with recycled thread objects reused when creating new
 # threads. This is required for programs that sequentially create many short living threads