View Issue Details

IDProjectCategoryView StatusLast Update
0000740XdebugStep Debuggingpublic2020-03-12 16:51
Reporternnmatveev Assigned Toderick  
PriorityhighSeveritymajorReproducibilityhave not tried
Status resolvedResolutionno change required 
Summary0000740: Allow to send 'eval' command after reaching of 'stopping' state
Description

Personally I need it to provide better integration of Xdebug code coverage and IDE PhpStorm.

The existing way to enable/disable code coverage and getting coverage result is handy for command line tools (like PHPUnit), but absolutely unusable for IDEs.

The ultimate goal is to get code coverage data of any php script (local or remote) without bootstrapping it.

My current vision of such integration (over existing DBGP protocol):
1) <- init message
2) -> eval('xdebug_start_code_coverage()')
3) -> run
4) <- run response (state='stopping')
5) -> eval('xdebug_get_code_coverage()')
6) -> run
---finish of the execution

TagsNo tags attached.
Operating System
PHP Version5.3.8

Activities

derick

2014-02-27 19:14

administrator   ~0002692

When stopping is reached, the executor is shutdown. What would be a much better solution is to allow coverage information to be dumped over DBGp. Wouldn't you agree?

derick

2014-05-19 23:17

administrator   ~0002823

When stopping is reached, the executor is shutdown. What would be a much better solution is to allow coverage information to be dumped over DBGp. Wouldn't you agree?

derick

2016-12-11 23:35

administrator   ~0004009

If the executor is shutdown, I can't run more commands. And no feedback was provided for my question.

I'm closing this for now.

Issue History

Date Modified Username Field Change
2011-10-24 22:38 nnmatveev New Issue
2014-02-27 19:14 derick Note Added: 0002692
2014-02-27 19:14 derick Assigned To => derick
2014-02-27 19:14 derick Status new => feedback
2014-05-19 23:17 derick Note Added: 0002823
2016-12-04 19:13 derick Status feedback => new
2016-12-11 23:35 derick Note Added: 0004009
2016-12-11 23:35 derick Status new => resolved
2016-12-11 23:35 derick Resolution open => no change required
2020-03-12 16:51 derick Category Feature/Change request => Step Debugging