Integrated: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote
Leonid Mesnik
lmesnik at openjdk.org
Tue Feb 24 19:44:57 UTC 2026
On Thu, 29 Jan 2026 01:35:57 GMT, Leonid Mesnik <lmesnik at openjdk.org> wrote:
> Hi
>
> Please review following fix that remove incorrect assertion.
>
> Verification should be always done for redefined classes, and is called
> `bool Verifier::verify(InstanceKlass* klass, bool should_verify_class, TRAPS)`
> where `should_verify_class` and `is_eligible_for_verification` define if verification should be done or not.
> Thus, seems it doesn't make a sense to check `BytecodeVerificationRemote` during verification.
>
> Verified that class redefinition tests pass now with TEST_VM_OPTS="-XX:-BytecodeVerificationRemote" and fastdebug
This pull request has now been integrated.
Changeset: 9f89fa5b
Author: Leonid Mesnik <lmesnik at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/9f89fa5b67cb05166fa0d396412a2d6c48ca0ca6
Stats: 13 lines in 2 files changed: 7 ins; 3 del; 3 mod
8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote
Reviewed-by: dholmes, coleenp, sspitsyn
-------------
PR: https://git.openjdk.org/jdk/pull/29476
More information about the serviceability-dev
mailing list