[xdebug-dev] Bug 0000250: XDebug 2.0RC3 doesn't report error conditions

From: <noreply[@]lists.xdebug.org>
Date: Tue, 3 Apr 2007 16:47:19 +0200

The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000250
======================================================================
Reporter: mathieuk
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 250
Category: Usage problems
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Operating System: Tested on Windows & Linux
PHP Version: 5.2.0
Xdebug Version: 2.0.0rc3
Resolution: not a bug
======================================================================
Date Submitted: 2007-04-02 10:15 CEST
Last Modified: 2007-04-03 16:47 CEST
======================================================================
Summary: XDebug 2.0RC3 doesn't report error conditions
Description:
XDebug 2.0RC3 doesn't report any errors when an error occurs.

Consider the following script:
<?php

$test = "test";
waa();

?>

This should raise an undefined function error.

Configuration:
========================================================
No special configuration options set.

Expected behaviour:
========================================================
When running the above script through debugclient-0.9.0, after issueing
the 'run' command, xdebug should reply with a <response> element
indicating a problem (status=aborted?). It probably needs a <error>
element aswell, containing the error message.

Actual behaviour:
========================================================
The script runs and when it runs into the error, xdebug reports the script
now has the 'stopped' state with 'reason=ok':

debugclient-0.9.0 transcript:
-----------------------------

Connect
<?xml version="1.0" encoding="iso-8859-1"?>
<init fileuri="file:///data/home/mathieu/public_html/xd/index.php"
language="PHP" protocol_version="1.0" appid="9507" idekey="waa"><engine
version="2.0.0RC3"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick
Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright
(c) 2002-2007 by Derick Rethans]]></copyright></init>
(cmd) run -i waa
<?xml version="1.0" encoding="iso-8859-1"?>
<response command="run" transaction_id="waa" status="stopped"
reason="ok"></response>
(cmd)

======================================================================

----------------------------------------------------------------------
 mathieuk - 2007-04-03 10:05 CEST
----------------------------------------------------------------------
Same issue occurs with xdebug-cvs:

Transcript:

mathieu[@]ubuntu:~$ ./debugclient-0.9.0
Xdebug Simple DBGp client (0.9.0)
Copyright 2002-2004 by Derick Rethans.
- libedit support: enabled

Waiting for debug server to connect.
Connect
<?xml version="1.0" encoding="iso-8859-1"?>
<init xmlns="urn:debugger_protocol_v1"
xmlns:xdebug="http://xdebug.org/dbgp/xdebug"
fileuri="file:///home/mathieu/public_html/xdebug/index.php" language="PHP"
protocol_version="1.0" appid="6950" idekey="waa"><engine
version="2.0.0RC4-dev"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick
Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright
(c) 2002-2007 by Derick Rethans]]></copyright></init>
(cmd) run -i waa
<?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1"
xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="run"
transaction_id="waa" status="stopped" reason="ok"></response>

----------------------------------------------------------------------
 derick - 2007-04-03 16:47 CEST
----------------------------------------------------------------------
This is not a bug. In order for the debugger to stop on error or warning
conditions, you need to set a breakpoint on them. You can do that with:

breakpoint_set -i 71 -t exception -x "Fatal error"

Bug History
Date Modified Username Field Change
======================================================================
2007-04-02 10:15mathieuk New Bug
2007-04-02 10:15mathieuk Bug Monitored: mathieuk
2007-04-03 10:05mathieuk Bugnote Added: 0000583
2007-04-03 16:47derick Bugnote Added: 0000584
2007-04-03 16:47derick Assigned To => derick
2007-04-03 16:47derick Resolution open => not a bug
2007-04-03 16:47derick Status new => resolved
======================================================================
Received on Tue Apr 03 2007 - 16:47:23 BST

This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:03 BST