-
Bug
-
Resolution: Fixed
-
P3
-
8
-
Confirmed on x86, likely on other architectures.
-
b53
-
x86
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8026083 | 8 | David Chase | P3 | Resolved | Fixed | b111 |
Various ute "defmeth" tests fail when a NullPointerException is thrown instead of an AbstractMethodError.
This occurs 24 times across a variety of cases in two different tests. These failures can be seen in the attached file which includes the failing cases from a logfile.
The cause of this appears to be failure to translate null pointer exceptions into abstract method errors occurring in code compiled by methodHandles_x86.cpp. It appears that NPE->AME is the convention; see vtableStubs_x86.cpp, for example (search for ame_addr) and templateTable_x86_32.cpp (search for no_such_method).
A fix can be applied to jump_from_method_handle in methodHandles_x86.cpp.
This occurs 24 times across a variety of cases in two different tests. These failures can be seen in the attached file which includes the failing cases from a logfile.
The cause of this appears to be failure to translate null pointer exceptions into abstract method errors occurring in code compiled by methodHandles_x86.cpp. It appears that NPE->AME is the convention; see vtableStubs_x86.cpp, for example (search for ame_addr) and templateTable_x86_32.cpp (search for no_such_method).
A fix can be applied to jump_from_method_handle in methodHandles_x86.cpp.
- backported by
-
JDK-8026083 Methodhandles/JSR292: NullPointerException (NPE) thrown instead of AbstractMethodError (AME)
-
- Resolved
-
- relates to
-
-
- Resolved
-