[news.eclipse.tools.php] Re: Problems with PDT and Xdebug

[Dave Kelsey <dkel50@xxxxxxxxxxx>]

> Thanks Dave, I did not understand that about the ports. I have changed 
> and this is what I see:
>
> - If I "Run PHP Script" I can not have the "Run With Debug Info" checked 
> else I get this error:
>
>   "Error launching 'phpinfo' The debug session could not be started.
>    Please make sure the debugger is properly configured.
>
>
> - If I "Run PHP Script" with "Run With Debug Info" not checked it runs 
> but all output is written to the console tab. I am not sure if that is 
> the correct behavior.

I dont understand what "Run With Debug info" does either. I have raised a bugzilla
about this for the PDT developers to address. The only thing I can recommend is that
you do not have "Run With Debug Info" checked. Output of your script is written
to the console tab which is where I would expect the output of a standalone script
executable to be written.


> - No problems with "Run as PHP Web Page".
>
>
> - If I "Debug as PHP Script" and it defaults to "Brake at first line" I 
> get this error:
>
>   "Error launching 'phpinfo' The debug session could not be started.
>    Please make sure the debugger is properly configured.
>
>
> - If I "Debug as PHP Web Page" and I put a STOP on the line that issues 
> the 'phpinfo()' command. It just displays the output in a tab next to 
> the program source tabs. The PHP Debug perspective does even open up.

You are trying here to use the Zend Debugger so you would need to get
the PDT developers to reply to. I suggest you ask on a new forum append
about these errors.

> - If I "Debug as Web Script with Xdebug" and it defaults to "Brake at 
> first line" a new "Internal Web Browser" tab open up down alongside of 
> the console tab. It just stays there with the red button saying it is 
> running but nothing happens. I do not see a URL in the input line for 
> the internal web browser.

Did the debug session launch and show that you are stopped on the first line ?
What has happened is that the web browser has requested a page, the server is
halted returning the information because you have stopped on the first line so
your browser is still waiting for the rest of the page to be sent. The URL may not
be displayed in the internal browser until the page is completely sent from the
web server.

Dave Kelsey