Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126132
Precedence: bulk
MIME-Version: 1.0
References: <CA+NMNO1zgCLLDOaWhqg8ipOrLETRn3w_91JNdCJz0zrKmeRWyg@mail.gmail.com>
 <CA+NMNO07m0EpBcNLWuR1dPvhoTdVFkHk=Z=ziw41SRLFMo_-uA@mail.gmail.com>
In-Reply-To: <CA+NMNO07m0EpBcNLWuR1dPvhoTdVFkHk=Z=ziw41SRLFMo_-uA@mail.gmail.com>
Reply-To: erictnorris@gmail.com
Date: Tue, 17 Dec 2024 13:55:38 -0500
Message-ID: <CA+NMNO2N-o8oHK6OzTEg_J+tm2fEuMOMW=OxPwq2S8uuD41dng@mail.gmail.com>
Subject: [PHP-DEV] Re: [RFC] [Discussion] Error backtraces v2
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: eric.t.norris@gmail.com (Eric Norris)

On Mon, Dec 16, 2024 at 11:17=E2=80=AFAM Eric Norris <eric.t.norris@gmail.c=
om> wrote:
>
> Hello,
>
> We're nearing the two-week mark, so I'm curious if anyone has any
> other feedback or points of discussion for this RFC.
>
> In particular, I'm interested to know if anyone has thoughts on a
> suggestion I had in one of the reply threads - that we could consider
> something to the effect of allowing a user-supplied function for fatal
> errors - and if that is worth pursuing. If not, I'll continue with the
> RFC as-is and plan to put it up for a vote when eligible.
>
> Thanks!

I've added a voting choice, "If fatal_error_backtraces defaults to 1,
default value in run-tests.php", in response to discussion in the
GitHub PR.