Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmatched onFinish in ContractionTimerDistilled #18

Open
ftc opened this issue Jan 6, 2017 · 1 comment
Open

Unmatched onFinish in ContractionTimerDistilled #18

ftc opened this issue Jan 6, 2017 · 1 comment

Comments

@ftc
Copy link
Member

ftc commented Jan 6, 2017

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.

@ftc
Copy link
Member Author

ftc commented Jan 6, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant