FA-90042 / Bytecode virtual machines / Member archive

Constant pool: Fieldref entries unresolvable · case 02

getfield/putfield operands resolve to bad-ref errors.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

pool lists entries in file order; indexes start at 1 and Long/Double entries occupy two indexes (the second is unusable). Resolution: Utf8 -> text; Integer/Long/Double -> value; String -> quoted Utf8 text; Class -> Utf8 binary name with "/" turned into "."; NameAndType -> "name:descriptor"; Methodref and Fieldref -> "Class.name:descriptor" where the owner must be a Class entry and the second index a NameAndType. Any index that is missing or of the wrong kind yields ["bad-ref", index].

Why this case matters

Class loaders and interpreters must resolve symbolic references against the exact pool layout.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
field reference	`[["bad-ref", 14]]`	`["java.lang.String.length2:()I"]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.