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

未关闭
#2,102 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
java, perl
领域
backend, testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Perl
星标
67
派生
8
平均合并
5 小时 12 分钟
30 天内合并 PR
131

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。