Running the auto tracer on the ContractionTimerDistilled on the tracer vm ( ubuntu@192.12.243.135) results in a unmatched method entry in the noCrash trace for the non crashing trace.
This appears to not have anything to do with the auto tracer, the auto tracer just causes it to crash and that is the input I am using.
When the unmatched message at 485 in ctrace.py in cuplv/callback-verification is triggered the com.peilunzhang.contractiontimerdistilled.CountdownFragment$1.onFinish() is still on the stack.
Note: this may be due to auto tracer issues. The non crashing trace driver from the auto tracer emits a crashing trace and this crashing trace does not match up properly. When run through callback verification.
Running the auto tracer on the ContractionTimerDistilled on the tracer vm ( ubuntu@192.12.243.135) results in a unmatched method entry in the noCrash trace for the non crashing trace.
This appears to not have anything to do with the auto tracer, the auto tracer just causes it to crash and that is the input I am using.
When the unmatched message at 485 in ctrace.py in cuplv/callback-verification is triggered the com.peilunzhang.contractiontimerdistilled.CountdownFragment$1.onFinish() is still on the stack.