[xdebug-dev] Bug 0000217: stepping through code sometimes gives a wrong execution line

The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000217
======================================================================
Reporter: bhofmann
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 217
Category: Usage problems
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Operating System:
PHP Version: 5.1.6
Xdebug Version: 2.0.0rc1
Resolution: not fixable
======================================================================
Date Submitted: 2006-10-30 14:41 CET
Last Modified: 2006-10-30 14:52 CET
======================================================================
Summary: stepping through code sometimes gives a wrong execution line
Description:
When stepping trough this kind of code using step over:

if ($var){
        $test = "azerty";
}

Xdebug stops at the "if", then the test line: this is ok. However with
this code:

if ($var)
{
        $test = "azerty";
}

Xdebugs skips the "if" but steps on the opening curly brace, then steps on
the test line. And finally with this:

if ($var)
        $test = "azerty";

the "if" line is skipped and Xdebug step directly to the test line.
======================================================================

----------------------------------------------------------------------
 derick - 2006-10-30 14:52 CET
----------------------------------------------------------------------
This is something I can not fix unfortunately as the Zend Engine does not
always put the interception points on the correct line.

Bug History
Date Modified Username Field Change
======================================================================
2006-10-30 14:41bhofmann New Bug
2006-10-30 14:41bhofmann Bug Monitored: bhofmann
2006-10-30 14:52derick Bugnote Added: 0000487
2006-10-30 14:52derick Assigned To => derick
2006-10-30 14:52derick Resolution open => not fixable
2006-10-30 14:52derick Status new => resolved
======================================================================
Received on Mon Oct 30 2006 - 14:52:58 GMT