`print_r` should not produce a fatal error
Open
Nobody has claimed this yet.
- #7964 by @cmb69 — closed without merging
Category: Engine
Feature
Status: Verified
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
print_r (and any function calling __debugInfo()) should not produce a fatal error, it should generate an \Error exception instead
Contributor 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.
Research direction
Start with the reproduction at https://3v4l.org/YTfSl and trace the print_r and __debugInfo() entry points in the PHP source; no repository file or test is named in the issue. Done means these calls generate an Error exception instead of a fatal error, with regression coverage for the demonstrated case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100