-
Notifications
You must be signed in to change notification settings - Fork 353
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
Unable to verify EnsuresCalledMethods #6535
Comments
I think it's complaining because
Here are some test files from the RLC's test suite that should be useful for you to see what the checker can and cannot verify:
Here are the standard Hope this helps, and happy to answer any other questions! |
Thanks for the detailed reply. |
The checker might be overly conservative here; I haven't thought in detail about whether the absence of an |
I see, thanks for clarifying. I have a slightly unrelated question about the library annotations for the Socket class. I see an |
That's a fair point. However, because
The reason is exactly the one that you gave - that is:
|
Makes sense. I have no further questions. Thank you for your prompt response! |
Closing this issue, since all questions have been answered. |
The following code generates the below error with the resource leak checker.
Why does the checker complain of no information about this.socket1, though it is closed? What is the right way to close the two sockets such that the checker can verify both the annotations?
I am using version 3.43.0 of the checker framework. Also, I would appreciate it if someone could point me to the library annotations for the Socket class. Thanks!
The text was updated successfully, but these errors were encountered: