Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129479
Date: Mon, 1 Dec 2025 10:36:51 +0000 (GMT)
To: "Marc B." <marc@mabe.berlin>
cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] Possibility to include called object in exception
 backtrace
In-Reply-To: <6f3167c3-b6e7-4f25-8154-ce20de7d3e82@mabe.berlin>
Message-ID: <1c04232d-5a9c-16c7-b01b-1469d566aefa@php.net>
References: <6f3167c3-b6e7-4f25-8154-ce20de7d3e82@mabe.berlin>
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1609456599-1764585411=:29692"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1609456599-1764585411=:29692
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Sat, 29 Nov 2025, Marc B. wrote:

> I have opened a simple PR to add the possibility to include called=20
> object in exception backtrace.
>=20
> https://github.com/php/php-src/pull/20599
>=20
> This needs=C2=A0a discussion here to see if there are objections.
>=20
> About the patch:
>=20
> The patch adds the ability to populate the called |object| into=20
> exception backtraces.

I do this in Xdebug (as part of https://bugs.xdebug.org/1562) and it's=20
causing some issues with fframeworks/applications that rely on=20
destructors being called at a specific time, or in a specific order:=20
https://bugs.xdebug.org/2222

The Xdebug situation is probably a little worse, as I keep that last 8=20
exception traces *too*, but I am sure this is going to trip up people.

>=20
> Previously, only |debug_backtrace()| could include the called object=20
> in its frames, but |Exception::getTrace()| could not. This change=20
> aligns |Exception::getTrace()| with |debug_backtrace()| by introducing=20
> a new INI directive:
>=20
> |zend.exception_provide_object (boolean)|

I don't think that adding an INI setting (again) is a good idea. If you=20
want to make this configurable, it should be an option on=20
Exception::getTrace() =E2=80=94 INI settings make applications less portabl=
e=20
(even though this is a debugging option).

cheers,
Derick
--8323329-1609456599-1764585411=:29692--