[interpreter] Capture::Tiny fails when duplicating STDOUT during capture

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

Research direction

Start with the interpreter’s filehandle duplication path used by Capture::Tiny::_capture_tee → _open_std → _open, where dup mode on STDOUT fails with Bad file descriptor; issue #1165 may provide related context. First run the minimal reproducer with system Perl, the JVM backend, and the interpreter, then locate the project-owned regression tests for filehandle duplication. Done means the reproducer and Duadua’s t/50_cli.t pass under both PerlOnJava backends, with the full upstream suite passing under the interpreter.

Written by the indexing model from the issue text.

Description

area:backend area:io bug

Summary

Capture::Tiny output capture fails on the PerlOnJava interpreter. Duadua 0.36's t/50_cli.t uses Capture::Tiny and exits before completing its assertions when run with the interpreter. The same test passes under system Perl and the PerlOnJava JVM backend.

This was found while investigating CPAN random run 20261109-091152-39587. That run's archived default-backend log ends after t/15_reparse.t without a harness summary, so its Unknown test outcome is inconclusive and is not evidence for this interpreter failure. The full Duadua suite passes under system Perl and under the default PerlOnJava launcher/JVM backend (6 files, 490 tests).

Minimal reproducer

use Capture::Tiny qw(capture);
my ($stdout, $stderr) = capture { print "captured\n" };
die "unexpected capture: $stdout" unless $stdout eq "captured\n";
die "unexpected stderr: $stderr" if length $stderr;
print "capture ok\n";

Run the program with system Perl, the PerlOnJava JVM backend, and the PerlOnJava interpreter backend.

Results

  • System Perl 5.42.2: prints capture ok and exits 0.
  • PerlOnJava JVM backend: prints capture ok and exits 0.
  • PerlOnJava interpreter backend: fails before the capture callback completes with Bad file descriptor while Capture::Tiny duplicates STDOUT.
  • Duadua 0.36 t/50_cli.t: passes under system Perl and the JVM backend; under the interpreter it exits with status 255 after 9 assertions, before done_testing.

The failing call path is Capture::Tiny::_capture_tee -> _open_std -> _open. _open_std opens STDOUT in dup mode (>&); _open reports the bad descriptor. The reproducer uses the pure-Perl Capture::Tiny 0.50 module.

Environment

  • macOS 26.7.1
  • OpenJDK 24.0.2 (Temurin)
  • PerlOnJava launcher built from local master commit 13db7bd4a0 (2026-11-05)
  • Duadua 0.36; Capture::Tiny 0.50

Related issue

Issue #1165 fixed duplication of a tied filehandle. This reproducer is a separate interpreter failure in Capture::Tiny's ordinary capture path; the JVM backend succeeds.

Acceptance criteria

  • The minimal reproducer succeeds on both PerlOnJava backends and system Perl.
  • Duadua 0.36 t/50_cli.t and the full upstream suite pass under the interpreter.
  • Add a focused project-owned regression test validated with system Perl first.
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.