Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126110
Precedence: bulk
MIME-Version: 1.0
Reply-To: erictnorris@gmail.com
Date: Thu, 5 Dec 2024 15:57:48 -0500
Message-ID: <CA+NMNO1zgCLLDOaWhqg8ipOrLETRn3w_91JNdCJz0zrKmeRWyg@mail.gmail.com>
Subject: [PHP-DEV] [RFC] [Discussion] Error backtraces v2
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: eric.t.norris@gmail.com (Eric Norris)

Hello yet again internals,

I'd like to formally propose a continuation of the original error
backtraces RFC (https://wiki.php.net/rfc/error_backtraces):

https://wiki.php.net/rfc/error_backtraces_v2

We recently had a production incident that might have been shortened,
had we been able to identify an errant infinite loop in our code from
the backtrace of a PHP timeout error. It's likely that there are
plenty of other error conditions that would be easier to debug with a
stacktrace, too.

The original RFC is inactive, but I've read the proposal and resulting
discussion and I believe that @nikic's suggestion is a viable way to
address the RFC's issues. I've implemented that suggestion here:

https://github.com/php/php-src/pull/17056

The RFC currently has two voting choices, the first is to accept an
INI setting to configure an error mask for backtraces, and the second
is to choose the default value for the error mask.

Please take a look at let me know what you think.

Thank you!