Class::Throwable interpreter reports source line one too late

Open
#2,042 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
perl
Domain
compilers

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::Throwable 0.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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.