The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000297
======================================================================
Reporter: d_kelsey
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 297
Category: Usage problems
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Operating System: Windows.
PHP Version: 5.2.1
Xdebug Version: 2.0.0rc5-dev
Resolution: not a bug
======================================================================
Date Submitted: 2007-07-19 14:59 CEST
Last Modified: 2007-07-20 00:21 CEST
======================================================================
Summary: XDebug doesn't report back the transaction id on error response
Description:
An example of a command I sent to XDebug 2.0.0 (full version) and the
response I got
-->DBGp: cmd: breakpoint_set -i 125 -t line -f
file:///C:/udata-eclipse/testworkspaces/testxdebug/PhpCode/Looping.php -n
9 -- JGkgPT0gMTAw
-->DBGp: Response: <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1"
xmlns:xdebug="http://xdebug.org/dbgp/xdebug"
command="breakpoint_set"><error code="3"><message><![CDATA[invalid or
missing options]]></message></error></response>
I get a bad response back, but not transaction id is in the response. The
DBGp protocol doc includes it in the example.
======================================================================
----------------------------------------------------------------------
derick - 2007-07-19 19:50 CEST
----------------------------------------------------------------------
I can not reproduce this, the only time I do not get a transaction ID back
in the response is when the transaction ID was not part of the command
either:
(cmd) breakpoint_set -i 125 -t line -f
file:///C:/udata-eclipse/testworkspaces/testxdebug/PhpCode/Looping.php -n
9 -- JGkgPT0gMTAw
<?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1"
xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set"
transaction_id="125" id="21740001"></response>
(cmd) fsad
<?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1"
xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="fsad"><error
code="3"><message><![CDATA[invalid or missing
options]]></message></error></response>
----------------------------------------------------------------------
d_kelsey - 2007-07-19 22:21 CEST
----------------------------------------------------------------------
HI Derick, apologies, my output of the command was not correct, It turns
out I was putting the transaction id at the end of the command ie
breakpoint_set -t line -f
file:///C:/udata-eclipse/testworkspaces/testxdebug/PhpCode/Looping.php -n
9 -- JGkgPSAxMDA= -i 71
and so it wasn't picking up the transaction id, So I can fix this by
putting the transaction id between the command and the command arguments
(which are all the specific command arguments).
Don't know if you want to keep this open as xdebug didn't allow for
arguments after the --.
Sorry about the confusion.
----------------------------------------------------------------------
derick - 2007-07-20 00:21 CEST
----------------------------------------------------------------------
Okay, no worries. I'll close it then as this is not a bug. I did however
find an invalid free problem with the condition which could make Xdebug
crash when PHP was shutting down. I fixed that in CVS now.
Bug History
Date Modified Username Field Change
======================================================================
2007-07-19 14:59d_kelsey New Bug
2007-07-19 14:59d_kelsey Bug Monitored: d_kelsey
2007-07-19 19:50derick Bugnote Added: 0000699
2007-07-19 19:50derick Status new => feedback
2007-07-19 22:21d_kelsey Bugnote Added: 0000701
2007-07-20 00:21derick Bugnote Added: 0000702
2007-07-20 00:21derick Assigned To => derick
2007-07-20 00:21derick Resolution open => not a bug
2007-07-20 00:21derick Status feedback => resolved
======================================================================
Received on Fri Jul 20 2007 - 00:21:14 BST
This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:03 BST