-
Notifications
You must be signed in to change notification settings - Fork 578
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
False positive SE_PREVENT_EXT_OBJ_OVERWRITE #2750
Comments
Hello! I'll check it early next week. |
PatrikScully
added a commit
to PatrikScully/spotbugs
that referenced
this issue
Dec 11, 2023
1 task
hazendaz
added a commit
to PatrikScully/spotbugs
that referenced
this issue
Dec 12, 2023
hazendaz
added a commit
that referenced
this issue
Dec 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The logic to detect
readExternal()
guards introduced in #2426 requires a very strict shape of the guard.The first example is:
This differs from
GoodExternalizableTest
only in the bytecode shape, code reachability remains exactly the same.A second example, common when using Externalizable Serialization Proxies, is:
Here the difference is the use of IFNULL/IFNONNULL instead of IFEQ/IFNE to check state.
The text was updated successfully, but these errors were encountered: