[xdebug-dev] Bug 0000091: breakpoint_remove is not behaving as documented

The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000091
======================================================================
Reporter: spookwork
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 91
Category: Documentation
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Operating System: Windows
PHP Version: 4.3.8
Xdebug Version: 2.0-dev
Resolution: unable to duplicate
======================================================================
Date Submitted: 2004-09-09 18:02 CEST
Last Modified: 2004-09-18 09:54 CEST
======================================================================
Summary: breakpoint_remove is not behaving as documented
Description:
During execution my IDE issued the command "breakpoint_remove -i TID -d
BID" but the response was always a 204 which referred to an improper
STATE. In the documentation the STATE option is used with
breakpoint_update but is not used with breakpoint_remove. Attempting to
remove the association to the breakpoint with "breakpoint_update -i TID -d
BID -s disabled" returned an error "3".

The final solution was found by using the following command:
"breakpoint_remove -i TID -d BID -s disabled"
======================================================================

----------------------------------------------------------------------
 derick - 2004-09-18 09:54 CEST
----------------------------------------------------------------------
This works fine for me:

<init fileuri="file:///home/derick/test.php" language="PHP"
protocol_version="1.0" appid="3099" idekey="xdebul1"><engine
version="2.0.0beta1"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick
Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright
(c) 2002-2004 by Derick Rethans]]></copyright></init>

(cmd) breakpoint_set -i 1 -f test.php -n 2
<response command="breakpoint_set" transaction_id="1" status="starting"
reason="ok"><error code="3"></error></response>

(cmd) breakpoint_set -i 1 -t line -f test.php -n 2
<response command="breakpoint_set" transaction_id="1"
id="30990001"></response>

(cmd) breakpoint_remove -i 2 -d 30990001
<response command="breakpoint_remove" transaction_id="2"><breakpoint
type="line" filename="file:///home/derick/test.php" lineno="2"
state="enabled" id="30990001"></breakpoint></response>

(cmd) breakpoint_list -i 3
<response command="breakpoint_list" transaction_id="3"></response>

(cmd) breakpoint_set -i 4 -t line -f test.php -n 2
<response command="breakpoint_set" transaction_id="4"
id="30990002"></response>

(cmd) breakpoint_list -i 5
<response command="breakpoint_list" transaction_id="5"><breakpoint
type="line" filename="file:///home/derick/test.php" lineno="2"
state="enabled" id="30990002"></breakpoint></response>

(cmd) breakpoint_remove -i 6 -d 30990001
<response command="breakpoint_remove" transaction_id="6" status="starting"
reason="ok"><error code="204"></error></response>

(cmd) breakpoint_remove -i 7 -d 30990002
<response command="breakpoint_remove" transaction_id="7" status="starting"
reason="ok"><error code="204"></error></response>

There are also no checks in the code that demand the -s option to be set
here.

Bug History
Date Modified Username Field Change
======================================================================
2004-09-09 18:02spookwork New Bug
2004-09-18 09:54derick Bugnote Added: 0000194
2004-09-18 09:54derick Assigned To => derick
2004-09-18 09:54derick Resolution open => unable to duplicate
2004-09-18 09:54derick Status new => resolved
======================================================================
Received on Sat Sep 18 2004 - 09:54:48 BST