[xdebug-dev] Bug 0000297: XDebug doesn't report back the transaction id on error response

The following NEW bug has been ADDED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000297
======================================================================
Reporter: d_kelsey
Handler:
======================================================================
Project: Xdebug
Bug ID: 297
Category: Usage problems
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Operating System: Windows.
PHP Version: 5.2.1
Xdebug Version: 2.0.0rc5-dev
======================================================================
Date Submitted: 2007-07-19 14:59 CEST
Last Modified: 2007-07-19 14:59 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.
======================================================================

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
======================================================================
Received on Thu Jul 19 2007 - 14:59:16 BST