Class::Throwable interpreter reports source line one too late
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with assertion 29 in the Class::Throwable 0.13 interpreter test and compare its source-line result under system Perl and the PerlOnJava interpreter. Trace which eval/caller frame accounts for the 107-versus-108 difference, using the context in #1548 and #1945. Add a project-owned regression and confirm the focused test on both PerlOnJava backends.
Written by the indexing model from the issue text.
Description
Summary
The Class::Throwable 0.13 interpreter test has one remaining source-line mismatch in assertion 29: PerlOnJava reports line 108, while system Perl expects line 107.
Evidence
- Reported during the work tracked by #1548.
- System Perl focused regression passes.
- The JVM
Class::Throwable0.13 run passed 30/30. - The interpreter run still differed at assertion 29 (actual 108, expected 107).
- PR #1945 separately fixed eval-frame
caller()[4]behavior; this one-line source-location discrepancy remained afterward. - The caller metadata work in #1548 was merged in #2036, but this mismatch is a separate follow-up.
Expected behavior
The interpreter backend should report the same source line as standard Perl for the assertion 29 stack/source-location case (107 rather than 108).
Next steps
Reproduce the assertion under system Perl and PerlOnJava interpreter, identify which eval/caller frame contributes the off-by-one line, and add a project-owned regression validated on standard Perl before changing runtime behavior. Confirm the focused test on both PerlOnJava backends after the fix.
Related: #1548 (closed after the broader caller metadata fix in #2036); #1945 (eval-frame caller()[4] fix).
- Dominant language
- Perl
- Stars
- 67
- Forks
- 8
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 131
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
area:cpan-port area:parser bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fglock/PerlOnJava#2137 ·
Maintainers usually reply within 1 day
-
area:backend area:cpan-port area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fglock/PerlOnJava#2071 ·
Maintainers usually reply within 1 day
-
area:runtime documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fglock/PerlOnJava#1579 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
fglock/PerlOnJava#2157 ·
Maintainers usually reply within 1 day
All issues in fglock/PerlOnJava
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day