[Runtime] Carp::carp reports Java source location in compile-time attribute handlers

Open
#2,092 2 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
54/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, perl
Domain
backend

Research direction

Start by reading Attributes.java near line 402 and the runtime stack or source-location handling used by Carp::carp; the issue identifies the Java call into the compile-time attribute handler as the failing path. Add project-owned regression coverage for a :ATTR(CODE,BEGIN) handler that calls Carp::carp, then run it on system Perl and both PerlOnJava backends. Done means the warning reports the Perl source file and line on both backends.

Written by the indexing model from the issue text.

Description

area:backend area:runtime area:warnings bug

Summary

A compile-time custom code attribute handler that calls Carp::carp gets the PerlOnJava implementation file and line as its warning location. In the Attribute-RecordCallers 0.02 suite, the warning points to Attributes.java line 402 instead of the Perl test file t/03my.t, so the test's source-location assertion fails.

Reproduction

Install or add Attribute-RecordCallers 0.02 to @INC, then run its upstream test t/03my.t:

use 5.18.0;
use warnings;
use feature 'lexical_subs';
no warnings 'experimental::lexical_subs';
use Attribute::RecordCallers;

my @w;
BEGIN { $SIG{__WARN__} = sub { push @w, @_ }; }
my sub foo :RecordCallers { }
print $w[0];

The upstream test checks that the warning matches:

Ignoring RecordCallers attribute on anonymous subroutine at .*03my.t

System Perl 5.42.2 passes the complete distribution suite: 8 files, 64 tests. On PerlOnJava, the JVM and interpreter backends both emit:

Ignoring RecordCallers attribute on anonymous subroutine at Attributes.java line 402.

The archived CPAN run 20261117-153921-75160 fails only t/03my.t test 4: 63/64 assertions pass (1 of 8 test files fails).

Root cause

Attributes.java:402 invokes the Perl custom MODIFY_CODE_ATTRIBUTES handler during compilation. Attribute::RecordCallers calls Carp::carp from that handler. Carp's stack walk receives the Java implementation call site as the source location instead of the Perl compilation unit and line. The resulting warning therefore contains Attributes.java line 402 rather than t/03my.t.

This reproduces on both execution backends. It is a Perl source-location/runtime stack mapping issue, not an Attribute-RecordCallers dependency or environment failure; the distribution is pure Perl and passes on system Perl.

Expected behavior

Warnings emitted by Carp::carp in compile-time attribute handlers should identify the Perl source file and line where the attribute is being applied, matching system Perl.

Related issues

Issues #1656 and #1666 addressed Carp::croak locations through Moo-generated eval/destructor wrappers. This report is a distinct reproducible Carp::carp location failure during compile-time attribute application; the existing fixes do not correct this case.

Suggested regression coverage

Add a project-owned test for a compile-time custom :ATTR(CODE,BEGIN) handler that calls Carp::carp, asserting that the warning location names the Perl source file rather than a Java implementation file. Validate the test on system Perl and both PerlOnJava backends.

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.