Bug #16565 Updated: Support for profiling/function tracking
| From: | henno dot taht at japauto dot ee | Date: | Sat, 29 Jun 2002 21:03:50 +0000 |
| Subject: | Bug #16565 Updated: Support for profiling/function tracking | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-12541@lists.php.net to get a copy of this message | ||
ID: 16565
Updated by: henno.taht@japauto.ee
Reported By: marv@cyberia.net.lb
Status: Closed
Bug Type: Feature/Change Request
Operating System: Any
PHP Version: 4.1.2
New Comment:
The second thing is quite useful if you don't want to go through all
the trouble setting up a working debugger.
Previous Comments:
------------------------------------------------------------------------
[2002-04-12 07:00:56] mfischer@php.net
There are quite a couple of debuggers/profilers out there.
------------------------------------------------------------------------
[2002-04-12 06:58:34] marv@cyberia.net.lb
In complicated scripts, its a big effort tracking function calls to
understand just whats going on. When you're trying to code for
effeciency, you need detailed function calling and timing information.
The ticks thing is a step forward, but it doesnt have any context
information.
I'm requesting two things. The first is a ticks variant on the function
level. You can register a function that gets called on every function
call (and maybe another on every function exit). Its important that the
callback is supplied with at least the function's name, so it can
recognize the context. Supplieng it with arguments would be a plus.
The second thing would be exposing the function call stack, so you
could see the caller of the current function, and its caller, all the
way to the top. Being able to retrieve the time the function was called
(in msecs) would be very good, but could be expensive.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16565&edit=1