View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001116XdebugStep Debuggingpublic2015-02-25 16:582021-03-17 08:56
Reporterrobertbasic Assigned Toderick  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionwon't fix 
Product Version2.3.1 
Summary0001116: Xdebug sends a stopping status message after a stopped status message
Description

When sending a "stop" command to the debugger after a command that sets the status to "break", for example after a "step_into", xdebug will send two response messages back to the debugging server.

The first one will be the correct response with status "stopped" and immediately after that a response with status "stopping".

I assume the "stopping" status is incorrect because, as per the dbgp docs, interaction is not possible after a "stopped" status (docs http://xdebug.org/docs-dbgp.php#status).

The "stopping" response can be seen in xdebug's remote_log file.

The debugclient only shows the "stopped" response, doesn't show the "stopping" response.

Steps To Reproduce

Start debugclient, start an xdebug session, issue first command in debugclient as "step_into -i 1", issue second command as "stop -i 2", in the remote_log there are two response messages for transaction 2, the first one with status "stopped", the second with status "stopping".

Additional Information

Reproduced on both xdebug 2.3.1 and 2.2.7 on PHP 5.6.6 and PHP 5.5.9.

Xdebug configuration is minimal with

xdebug.remote_enable=1
xdebug.remote_port=9000
xdebug.remote_log=/tmp/xdebug.log

Attached a screenshot of terminals with the steps (debugclient, www-browser, tail of the log file)

TagsNo tags attached.
Attached Files
xdebug.png (386,633 bytes)
Operating SystemFedora, Ubuntu
PHP Version5.6.5-5.6.9

Activities

derick

2016-12-11 23:34

administrator   ~0004007

Is this still a problem for you? You are probably right, but I'm wondering how important this is.

robertbasic

2016-12-12 06:48

reporter   ~0004034

As far as I can tell, it doesn't interfere with anything. This report is more of a "let's conform to the standard if possible" report rather than a bug report :)

derick

2016-12-12 11:15

administrator   ~0004036

Okay. I'll leave it around for now. But unlikely to get much attention any time soon.

derick

2021-03-17 08:56

administrator   ~0005730

I'm closing this ticket, as it's now so long ago, and I haven't heard further reports about this.

Issue History

Date Modified Username Field Change
2015-02-25 16:58 robertbasic New Issue
2015-02-25 16:58 robertbasic File Added: xdebug.png
2016-12-11 23:34 derick Note Added: 0004007
2016-12-11 23:34 derick Assigned To => derick
2016-12-11 23:34 derick Status new => feedback
2016-12-12 06:48 robertbasic Note Added: 0004034
2016-12-12 06:48 robertbasic Status feedback => assigned
2016-12-12 11:15 derick Note Added: 0004036
2016-12-12 11:15 derick Status assigned => acknowledged
2020-03-12 16:51 derick Category Feature/Change request => Step Debugging
2021-03-17 08:56 derick Status acknowledged => resolved
2021-03-17 08:56 derick Resolution open => won't fix
2021-03-17 08:56 derick Note Added: 0005730