-
Bug
-
Resolution: Fixed
-
P4
-
18
-
b21
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8276068 | 17.0.3-oracle | Harold Seigel | P4 | Resolved | Fixed | b01 |
JDK-8279306 | 17.0.3 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8276065 | 11.0.15-oracle | Harold Seigel | P4 | Resolved | Fixed | b01 |
JDK-8278496 | 11.0.15 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
verify_error(ErrorContext::bad_type(bci,
current_frame->stack_top_ctx(),
TypeOrigin::implicit(current_type())),
"Bad access to protected data in getfield");
The bad access could be caused by a putfield. So, the message should not be hardwired to say 'getfield'.
- backported by
-
JDK-8276065 Incorrect verifier protected access error message
- Resolved
-
JDK-8276068 Incorrect verifier protected access error message
- Resolved
-
JDK-8278496 Incorrect verifier protected access error message
- Resolved
-
JDK-8279306 Incorrect verifier protected access error message
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/99870b4b
-
Commit openjdk/jdk17u-dev/15f24065
-
Commit openjdk/jdk/e39bdc9d
-
Review openjdk/jdk11u-dev/691
-
Review openjdk/jdk17u-dev/11
-
Review openjdk/jdk/6042