Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 14
Affects Version/s: 8, 9, 10, 11
Component/s: core-libs
Labels:
- release-note=no

Subcomponent:
java.lang:class_loading
Resolved In Build:
b14

As part of the investigation of ~~JDK-8181144~~, it has been noticed that Class.forName, with initialize=false, can return a class that has not been linked. This conflict between the spec and implementation needs to be investigated and resolved.

blocks

JDK-8227926 add new JVM TI and JDI tests for classes loaded by Class::forName

Closed

csr for

JDK-8222071 Class.forName may return a reference to a loaded but not linked Class

Closed

relates to

JDK-8233091 Backout JDK-8212117: Class.forName loads a class but not linked if class is not initialized

Resolved

JDK-8230937 Update bugid in ProblemList for vmTestbase/nsk/jdb/eval/eval001/eval001.java

Resolved

JDK-8231924 Field::getGenericType triggers loading and linking that may fail with LinkageError

Closed

JDK-8181144 JDI - VirtualMachine.allClasses() does not return loaded but uninitialized class

Closed

JDK-8233272 The Class.forName specification should be updated to match the long-standing implementation with respect to class linking

Closed

JDK-8226540 Tighten spec around class loading/resolving/linking

Closed

JDK-8227926 add new JVM TI and JDI tests for classes loaded by Class::forName

Closed

JDK-8233260 Class.forName should be able to load, but not link, a class

Closed

(5 relates to)

1.	Update ProblemList for vmTestbase/nsk/jdb/eval/eval001/eval001.java		Resolved	David Holmes
2.	Release Note: Classes are now loaded and linked by Class.forName()		Closed	Brent Christian

Assignee:: Brent Christian

Reporter:: Alan Bateman

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2018-10-12 04:13

Updated:: 2019-11-04 13:47

Resolved:: 2019-09-09 11:06

Details

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates