Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129499
Content-Type: multipart/alternative;
 boundary="------------xAnnU2J68U4mOVqMh0bF0Z08"
Message-ID: <c6db59c3-04c4-46f8-8b1f-54f400945fec@mabe.berlin>
Date: Tue, 2 Dec 2025 06:32:07 +0100
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] Possibility to include called object in exception
 backtrace
To: internals@lists.php.net
References: <6f3167c3-b6e7-4f25-8154-ce20de7d3e82@mabe.berlin>
 <1c04232d-5a9c-16c7-b01b-1469d566aefa@php.net>
 <5C76F995-1E1E-4683-842B-ACD6BB2D4785@rwec.co.uk>
Content-Language: en-US
In-Reply-To: <5C76F995-1E1E-4683-842B-ACD6BB2D4785@rwec.co.uk>
From: marc@mabe.berlin ("Marc B.")

This is a multi-part message in MIME format.
--------------xAnnU2J68U4mOVqMh0bF0Z08
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Derick,

On 01.12.25 12:44, Rowan Tommins [IMSoP] wrote:
> On 1 December 2025 10:36:51 GMT, Derick Rethans<derick@php.net> wrote:
>> I don't think that adding an INI setting (again) is a good idea. If you
>> want to make this configurable, it should be an option on
>> Exception::getTrace() — INI settings make applications less portable
>> (even though this is a debugging option).
>
> A parameter on the getter would mean every exception has to capture the references just in case they're used, which would definitely be a bad idea.
>
> If I remember rightly, the existing INI setting for capturing parameters was added precisely so that users could turn *off* collection in production builds.
>
> The same reasoning applies to other debugging settings, like skipping evaluation of assertions rather than silently discarding their results.

As Rowan already mentioned, adding a parameter to `getTrace()` would 
require every exception object to keep a reference of the called object 
just to make it retrievable if requested.

Configuring it as INI option - it can, and should, be turned off on 
production environments.

Also, the INI option `|zend.exception_provide_object` would be in line 
`||zend.exception_ignore_args` making it's use consistent with already 
existing behavior.|

> Regards,
>
> Rowan Tommins
> [IMSoP]

Regards,
Marc

--------------xAnnU2J68U4mOVqMh0bF0Z08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Derick,</p>
    <div class="moz-cite-prefix">On 01.12.25 12:44, Rowan Tommins
      [IMSoP] wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:5C76F995-1E1E-4683-842B-ACD6BB2D4785@rwec.co.uk">
      <pre wrap="" class="moz-quote-pre">On 1 December 2025 10:36:51 GMT, Derick Rethans <a class="moz-txt-link-rfc2396E" href="mailto:derick@php.net">&lt;derick@php.net&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">I don't think that adding an INI setting (again) is a good idea. If you 
want to make this configurable, it should be an option on 
<a class="moz-txt-link-freetext" href="Exception::getTrace()">Exception::getTrace()</a> — INI settings make applications less portable 
(even though this is a debugging option).
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">

A parameter on the getter would mean every exception has to capture the references just in case they're used, which would definitely be a bad idea. 

If I remember rightly, the existing INI setting for capturing parameters was added precisely so that users could turn *off* collection in production builds.

The same reasoning applies to other debugging settings, like skipping evaluation of assertions rather than silently discarding their results.</pre>
    </blockquote>
    <p>As Rowan already mentioned, adding a parameter to `getTrace()`
      would require every exception object to keep a reference of the
      called object just to make it retrievable if requested.</p>
    <p>Configuring it as INI option - it can, and should, be turned off
      on production environments.</p>
    <p>Also, the INI option `<code class="notranslate">zend.exception_provide_object`
        would be in line `</code><code class="notranslate">zend.exception_ignore_args`
        making it's use consistent with already existing behavior.</code></p>
    <p><span style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span></p>
    <blockquote type="cite"
      cite="mid:5C76F995-1E1E-4683-842B-ACD6BB2D4785@rwec.co.uk">
      <pre wrap="" class="moz-quote-pre">Regards,

Rowan Tommins
[IMSoP]
</pre>
    </blockquote>
    <p>Regards,<br>
      Marc</p>
  </body>
</html>

--------------xAnnU2J68U4mOVqMh0bF0Z08--