Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Stacktrace::Configurable loses anonymous caller metadata on both backends

Aperta
  • Qualcosa non va?
#1,548 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
perl
Ambito
compilers

Direzione di ricerca

Start by running the five failing upstream tests: t/003-percent_s.t, t/004-percent_f.t, t/100-l4p.t, t/101-l4p_charY.t, and t/102-l4p_recursion.t, on both PerlOnJava backends. Trace the shared caller-stack and frame-metadata path used by Stacktrace::Configurable and the Log::Log4perl stack-trace layouts. Done means a focused regression test preserves the standard-Perl expectations for anonymous names, arguments, package/source formatting, and deparse data on both backends.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:backend area:cpan-port bug

Summary

The CPAN distribution Stacktrace-Configurable-0.06 fails under PerlOnJava because PerlOnJava does not preserve the same caller metadata used by Stacktrace::Configurable and Log::Log4perl::Layout::PatternLayout::Stacktrace.

This was observed in CPAN random tester run 20260928-091741-26386 for Log::Log4perl::Layout::PatternLayout::Stacktrace.

Evidence

  • Standard Perl passes the complete upstream suite: 14 files, 84 tests.
  • PerlOnJava fails 14 subtests in 5 files:
    • t/003-percent_s.t
    • t/004-percent_f.t
    • t/100-l4p.t
    • t/101-l4p_charY.t
    • t/102-l4p_recursion.t
  • The failure reproduces on both the JVM backend and the interpreter backend.
  • The failure is deterministic and does not involve XS/native code, missing services, display requirements, or a timeout.

Observed mismatches

The expected stack frames include anonymous caller information and arguments, for example:

__ANON__ (Log::Log4perl::Logger=HASH(...), "msg")

PerlOnJava instead reports forms such as:

debug

or, on the interpreter backend:

debug (Log::Log4perl::Logger=HASH(...), "msg")

Additional failures show incorrect package/file-name formatting in %s and %f, and closure deparsing that returns the wrong body (1+1 instead of the expected 2). The recursion-protection assertion itself passes, so the defect is specifically in stack-frame identity/argument/source metadata rather than the whole logging path.

Scope

The affected behavior is used by both Stacktrace::Configurable and Log::Log4perl stack-trace layouts. Please investigate the shared caller-stack/frame metadata path, including anonymous-sub naming, argument capture, package/source-name normalization, and source/deparse information exposed to stack-trace formatters.

The original CPAN failure was recorded as 14 failed subtests in the run identified above. A focused project regression test should preserve the standard-Perl expectations from the five failing upstream tests and pass on both PerlOnJava backends.

Lingua principale
Perl
Stelle
64
Fork
6
Merge medio
4h 42m
PR unite (30g)
182

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fglock/PerlOnJava

Tutte le issue di fglock/PerlOnJava

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.