when the DBG stops at a conditional statement (like IF and WHILE) DBG doesn't stop at the command after the IF but execute it.

E.g.



using step by step debugging the debugger stops at line 1, 2 and 4. Isn't possible to let DBG stopping at each statements like other debuggers do (eclipse, Visual Studio...)

Thanks

PhpED and php debugger has nothing to do with this. It's a known bug in php itself. It does not insert necessary info for the 3nd line (per your sample).
Eclipse, that you mentioned, won't do it either

yes I know this is not a bug of phped; I thought it was a bug of dbg

Tnx for the response

BTW breakpoints for 3rd line on the code below will work fine

Is this to say that this will either never be supported or will magically become supported if DBG is fixed to support it? Is it a known bug with DBG (not sure who/where dbg is to submit such a report..)

thanks

I think dmitri is saying that this is a bug with PHP and not with DBG (which is written by dimitri). He can't make DBG do this because PHP itself is broken .

-r

I think I have an answere as to why the php debugger does not stop on line 3 of this code



And does stop on line 3 of this code.



If you look at the first example there is and
"if ($a==1) then a $a+5; in most programing languages that is called and inline if statement. Meaning that even though the IF statement and condition are on seperate lines the interperter ( and the debugger I guess see it as one line. So it is as if you had typed:


That is why the debugger does not see line three as a seperate line. in the first example. In the second example the { tell the interpertere and the debugger that there is a multi line IF block coming up and to treat line 3 as a seperate line.

rodericksimpson is correct. The only thing I'd add is that dbg should not let IDE to show those little blue dots on the gutter for the lines where breakpoint won't work.