Protoeditor and xdebug 2.0.0RC4
Brought to you by:
thiago_silva
Menu
▾
▴
Hi!
I'm trying to get xdebug 2.0.0RC4 and protoeditor 1.1beta3 to work with each other. the general communication seems to work but there are some things that don't work.
Eg. when I set breakpoints in the editor they seem to be ignored. Only the "break on start" seems to be done. But when I place an xdebug_break() in the code, Protoeditor stops execution at the right place.
I'm also not sure how "step over" should work. I expected it to step to the next code line in execution? But this seems not to be the case?
Maybe some of this is already fixed in a current svn version? Could anyone give a short hint how to compile a SVN checkout? I guess i have to call automake, but I'm not sure about the correct way. A quick listing of commands to issue would help me a lot with this.
Andi
I also have problems with breakpoints when using file soft links. You can fix this by either opening the files on their real location (and have apache/php read them from their real location, too), or add a debug site with path mappings.
"Step over" means that if you an in an if() condition, you don't want to step through every code line *in* the if block but want to resume after the block has finished:
===============
if ($a == $b) {
$b++;
$a--;
}
$b = $a;
===============
Having the debug cursor on the if() section and click "step over" would lead to $b = $a; being active next.
Compilation is mostly done by doing ./configure; make; make install
If there is no config script, call autoconf before. The INSTALL file in svn describes it.
"I'm trying to get xdebug 2.0.0RC4 and protoeditor 1.1beta3 to work with each other. the general communication seems to work but there are some things that don't work."
Yeah, problems involving xdebug2 have been reported previously. Unfortunately I still couldn't find the time to fix it.
"I'm also not sure how "step over" should work."
'Step over' usually means that a single statement or expression is a single step. This is in contrast with 'Step Into', wich does the same but it enters a subroutine in case the current step involves a call.
"Maybe some of this is already fixed in a current svn version? "
Unfortunately, it is not. In fact, I think the last version released and the svn version are pretty much the same.
"Could anyone give a short hint how to compile a SVN checkout? "
Usually, the only thing you have to do before configure/make/make install is "make -f Makefile.cvs" to bootstrap the build system. I don't know how this differs from executing autoconf directly, but it's the way kde apps usually do.
Thiago
Andi,
I could not replicate the breakpoint problem you informed (Im using PHP 5.2.3 and xdebug 2 RC4). Could you provide a test case?
Thanks,
Thiago