JVM caller(0) returns stale package in closure invoked by BEGIN

Open
#2,102 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, perl
Domain
backend, testing

Research direction

Start by tracing how JVM caller(0) resolves the active package for closures invoked in BEGIN blocks, using the ExtUtils::ParseXS::Node reproduction around line 5330. Add a focused regression that runs on system Perl, JVM, and interpreter backends, and verify the module loads without changing ExtUtils::ParseXS::Node::ISA. Then rerun the Bitcoin-Crypto 4.005 CPAN target and confirm setup reaches its test suite.

Written by the indexing model from the issue text.

Description

area:backend area:runtime bug

Summary

Loading ExtUtils::ParseXS::Node fails on the JVM backend because caller(0) inside a closure invoked from a BEGIN block reports a stale package. The closure then writes the new subclass's @ISA into ExtUtils::ParseXS::Node::ISA, corrupting the base class hierarchy. Interpreter and system Perl load the same module successfully.

This is a remaining caller-package case related to #1753 and its fix in #1754. That fix covers the Eval::Closure::Sandbox_N caller frame. This case occurs in ordinary package compilation in the large ExtUtils::ParseXS::Node source file.

Reproduction

The CPAN tester run 20261118-104825-43075 selected Bitcoin-Crypto 4.005. Its test suite never started in PerlOnJava. While resolving the Bitcoin::Secp256k1 configure dependency, loading ExtUtils::ParseXS::Node failed:

Recursive inheritance detected in hierarchy of class 'ExtUtils::ParseXS::Node'
BEGIN failed--compilation aborted at ExtUtils/ParseXS/Node.pm line 5330.

The relevant upstream code is structurally:

my $build_subclass;
BEGIN {
    $build_subclass = sub {
        my $class = caller(0);
        no strict 'refs';
        @{"${class}::ISA"} = $parent;
    };
}

package ExtUtils::ParseXS::Node::INCLUDE_COMMAND;
BEGIN { $build_subclass->(-parent => 'include') }

With JVM DFS tracing enabled, the first declaration creates the valid chain:

INCLUDE @ISA = [Node::include]
Node::include @ISA = [Node::oneline]
Node::oneline @ISA = [Node]
Node @ISA = []

At the INCLUDE_COMMAND declaration, caller(0) resolves to ExtUtils::ParseXS::Node rather than ExtUtils::ParseXS::Node::INCLUDE_COMMAND. The assignment therefore changes Node::ISA to [Node::include]. The subsequent traversal reports the resulting cycle:

Node @ISA = [Node::include]
Node::include @ISA = [Node::oneline]
Node::oneline @ISA = [Node]
CYCLE DETECTED! Node already in visiting set

This identifies a stale package result from the JVM caller/source-location mapping for a closure in a BEGIN block. The visible inheritance-cycle diagnostic is secondary: the Perl source declares a valid subclass chain, and the package misidentification mutates the wrong @ISA.

Results

  • PerlOnJava JVM backend: direct -MExtUtils::ParseXS::Node load fails with exit 255.
  • PerlOnJava interpreter backend: the same module load succeeds.
  • System Perl 5.42.2: the same module load succeeds.
  • System Perl CPAN oracle for Bitcoin-Crypto 4.005: 77 files, 715 tests, PASS.
  • PerlOnJava CPAN run: timed out during dependency setup, before Bitcoin-Crypto's tests began. The fallback Alien::Build setup subsequently stalled while downloading cmake; that stall is downstream of the incorrect caller package and corrupted @ISA.
  • Reproduced in checkout d800eff96c4ea7a6aaab5bb0c586c31e607f1220, Java 24.0.2, macOS, Perl 5.42.2.

Acceptance criteria

  • caller(0) inside the subclass-building closure invoked by a BEGIN block reports the package active at the call site on the JVM backend, including in a large source file with many BEGIN blocks.
  • Loading ExtUtils::ParseXS::Node succeeds on the JVM backend and leaves ExtUtils::ParseXS::Node::ISA unchanged.
  • Add a focused project-owned regression that passes on system Perl, JVM, and interpreter backends.
  • Re-run the Bitcoin-Crypto 4.005 CPAN target and confirm dependency setup reaches the target test suite.
Dominant language
Perl
Stars
67
Forks
8
Avg merge
5h 12m
Merged PRs (30d)
131

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.