View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000613||Xdebug||Profiling||public||2010-09-03 14:56||2020-03-12 16:47|
|Target Version||Fixed in Version|
|Summary||0000613: Allow starting/stoping/restarting the profiling|
|Description||It would be a good thing to allow the profiler to be controlled from the userland.|
This could especially be handy when you have to profile daemons, because if you call pcntl_fork then the file descriptors would be cloned.
This would cause that both instance would be outputting the profiling information to the same file, and which is far more worse: the file handler would be closed when the parent or any child exits.
|Tags||No tags attached.|
||This would be good to have, but with the current architecture it's really difficult to do. So I am not targeting this for a specific version.|
Starting and stopping like the function trace feature would be great. But would it be possible to fix it like 0000938 did for debugging forked processes, basically starting a new profile instance when the PID changes? Unfortunately none of the trigger mechanisms provided by xdebug.profiler_enable_trigger work with forked processes since the standard PHP request processing is not occurring.
Fixed issue 0000938: Improve support for debugging forked PHP scripts
|2010-09-03 14:56||Tyrael||New Issue|
|2010-09-03 14:56||Tyrael||PHP Version||=> 5.3.3|
|2010-09-03 14:56||Tyrael||Xdebug Version||=> 2.2.0-dev|
|2016-12-13 21:05||derick||Note Added: 0004040|
|2016-12-13 21:05||derick||Assigned To||=> derick|
|2016-12-13 21:05||derick||Status||new => acknowledged|
|2019-08-25 21:34||jimp||Note Added: 0005124|
|2020-03-12 16:47||derick||Category||Feature/Change request => Profiling|