JVM caller(0) returns stale package in closure invoked by BEGIN
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 55/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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::Nodeload 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 aBEGINblock reports the package active at the call site on the JVM backend, including in a large source file with manyBEGINblocks.- Loading
ExtUtils::ParseXS::Nodesucceeds on the JVM backend and leavesExtUtils::ParseXS::Node::ISAunchanged. - 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.
- Lingua principale
- Perl
- Stelle
- 67
- Fork
- 8
- Merge medio
- 5h 12m
- PR unite (30g)
- 131
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fglock/PerlOnJava
-
area:cpan-port bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
fglock/PerlOnJava#2153 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port area:parser bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
fglock/PerlOnJava#2137 ·
I maintainer di solito rispondono entro 1 giorno
-
area:backend area:cpan-port area:runtime bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
fglock/PerlOnJava#2071 ·
I maintainer di solito rispondono entro 1 giorno
-
area:runtime documentation enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
fglock/PerlOnJava#1579 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 62/100
fglock/PerlOnJava#2157 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fglock/PerlOnJava
Issue simili
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksApertateam-cli
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 93/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
inverse-inc/packetfence#9728 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(char-create): show the real reason a character is refusedForse già presa @baphomello l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno