Class::Throwable interpreter reports source line one too late

未關閉
#2,042 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
perl
領域
compilers

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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).

主要語言
Perl
星號
67
分支
8
平均合併
5 小時 12 分鐘
30 天內合併 PR
131

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。