bug: resolve qualified class method calls without subroutine recursion
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 30/100
Línea de trabajo
Start with the minimal reproducer in the body: run it on both the JVM and interpreter backends to confirm the Deep recursion and StackOverflowError. The bug is in how a fully qualified Class::Name->method invocant is resolved when a subroutine of the same name exists, so the parser or call-resolution code for class-method invocants is the place to look. Done means the reproducer prints Probe::Thing on both backends and existing direct-call and indirect-object tests still pass.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Data::ParseBinary v0.31 fails on PerlOnJava because its Struct helper recursively calls itself instead of invoking the Data::ParseBinary::Struct->create class method. The archived CPAN random-tester run 20261120-195805-13340 reports a StackOverflowError in t/01various.t; the system-Perl oracle passes all 275 tests.
The same reduced case fails on the current main launcher (build 2211d46023) on both the JVM and interpreter backends. System Perl passes it.
Root cause
A fully qualified class invocant is confused with a same-named fully qualified subroutine. In Data::ParseBinary, the helper Data::ParseBinary::Struct and the class package Data::ParseBinary::Struct share that name. Perl treats Data::ParseBinary::Struct->create(...) as a class method call. PerlOnJava routes the package token back to the existing Data::ParseBinary::Struct function, causing unbounded recursion.
The collision can be reduced without the CPAN distribution:
use strict;
use warnings;
package Probe;
sub Thing { return Probe::Thing->create(@_) }
package Probe::Thing;
sub create { return bless { name => $_[1] }, $_[0] }
package main;
my $thing = Probe::Thing();
print ref($thing), "\n";
Expected output under standard Perl:
Probe::Thing
PerlOnJava emits Deep recursion on subroutine "Probe::Thing" and then StackOverflowError on both backends. The stack repeats the Probe::Thing function at the Probe::Thing->create source line.
Control cases pass on PerlOnJava: using a scalar containing Probe::Thing as the method invocant, calling Probe::Thing::create(...) directly, and calling a static method on a package without a same-named subroutine. This isolates the failure to resolving the literal fully qualified class name when that name is also a callable subroutine.
CPAN evidence
- Distribution:
Data-ParseBinaryv0.31 (pure Perl) - Run:
20261120-195805-13340 - System Perl: all 275 tests pass
- PerlOnJava: 4 of 5 test programs fail after
t/01various.thitsStackOverflowError; the later parse errors are consequences of the missing TAP plans - Current main focused reproducer: JVM and interpreter both fail with the same recursion
Related issues
- #1166 covers valid fully qualified indirect-constructor forms such as
new HTTP::Response ...; it does not cover explicitClass::Name->method()syntax colliding with a same-named function. - #1222 tracks Perl-compatible deep-recursion warnings. This reproducer enters unintended recursion and overflows; it is a method-call resolution defect, not only a warning mismatch.
Acceptance criteria
- The minimal reproducer prints
Probe::Thingon both PerlOnJava backends without a recursion warning or stack overflow. - Existing direct subroutine and indirect-object parsing behavior remains intact.
Data-ParseBinaryv0.31 passes its upstream suite on both PerlOnJava backends.
- Lenguaje dominante
- Perl
- Estrellas
- 67
- Forks
- 8
- Merge medio
- 4 h 36 min
- PR fusionados (30 d)
- 123
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fglock/PerlOnJava
-
area:runtime bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
fglock/PerlOnJava#2164 ·
Los mantenedores suelen responder en 1 día
-
area:cpan-port bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
fglock/PerlOnJava#2153 ·
Los mantenedores suelen responder en 1 día
-
area:cpan-port area:parser bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
fglock/PerlOnJava#2137 ·
Los mantenedores suelen responder en 1 día
-
area:backend area:cpan-port area:runtime bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
fglock/PerlOnJava#2071 ·
Los mantenedores suelen responder en 1 día
-
area:runtime documentation enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
fglock/PerlOnJava#1579 ·
Los mantenedores suelen responder en 1 día
Todos los issues de fglock/PerlOnJava
Issues similares
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksAbiertoteam-cli
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 93/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
inverse-inc/packetfence#9728 ·
Los mantenedores suelen responder en 1 día
-
fix(char-create): show the real reason a character is refusedPosiblemente ocupada @baphomello la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día