php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #75459 debug_backtrace() should include the Closure object
Submitted: 2017-10-30 08:54 UTC Modified: 2017-11-12 04:22 UTC
From: hegostasla at 2emea dot com Assigned:
Status: No Feedback Package: *General Issues
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2017-10-30 08:54 UTC] hegostasla at 2emea dot com
Description:
------------
Precisely like it does with the object, it should include the closure object.
Currently it is very hard to figure out what is what.

The closure objects should also embed the file and line they were defined in, also for debugging purposes.

Thank you.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2017-10-30 09:07 UTC] daverandom@php.net
-Status: Open +Status: Feedback
 [2017-10-30 09:07 UTC] daverandom@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


Please provide some sample code demonstrating how you expect this to look.

Note also that:

- it is already possible to get the defining file and line via reflection
http://php.net/manual/en/reflectionfunctionabstract.getfilename.php
http://php.net/manual/en/reflectionfunctionabstract.getstartline.php

- for closures, the defining line and file doesn't always have an unambiguously useful meaning, e.g. for closures created with ReflectionFunction::getClosure(), should the defining file and line be the location of the method call that created the closure, or the location of the definition of the underlying function?
 [2017-11-12 04:22 UTC] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Feb 22 10:01:28 2024 UTC