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

[IchBin <weconsul@xxxxxxx>]

IchBin wrote:
> Dave Kelsey wrote:
> > > 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 scriptB
> > executable to be written.
>
> I was hoping to hear you say that it should have written to a 
> internal\external browser. Example the fact the info() output is data 
> interlaced with HTTP. But then I guess there would be no need for "Run 
> as PHP Web Page". I guess this Run Type must be for standalone script 
> that have a tty type output.
>
> > > - 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.
>
> I have no idea that this was ONLY for the Zend debugger. It would be 
> better to have this information mentioned in the PDT docs or different 
> external label that would associate this with the Zend debugger. Again I 
> guess I should have rationalized this since their is a "Debug as Web 
> Script with Xdebug".
>
> > > - 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 ?
>
> No... The PHP Debug perspective did not display...
>
> > 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. 
>
> This makes sense now. I guess the problem is that the PHP Debug 
> perspective is not opening up. I will try again  and manually open up 
> that perspective to see if it will reflect that state of this debug 
> session. If so I guess I can then step through the script else I guess a 
> bug... (?)
>
> > The URL may not
> > be displayed in the internal browser until the page is completely sent 
> > from the
> > web server.
>
> Makes sense... If I select the input dropdown field for the internal 
> browser I do see prior submitted HTML with the Xdebug info for those 
> particular xdebug sessions.
>
> > Dave Kelsey
OK I did some testing of "Debug as Web Script with Xdebug". This is what 
I see:

- select a script in the PHP perspective.
- run "Debug as Debug"
- Select "PHP Web Script as Xdebug" and fill in the information for 
launch. (Brake at first Line)
- select "debug" button
- Firefox pop up. This maybe a *problem* because in the 
preferences\General\Web Browser the "Use Internal Web Browser" is now 
grayed out. Will only let me use an external browser. That is weird 
because I had "Use Internal Web Browser" selected before running this 
debug session.
- I then manually open the PHP debug perspective.
- In the "Debug" tab, on the PHP Debug perspective, I have to open up 
the tree by selecting the entry under "PHP Thread". I think that this 
the current line pointer.
- The first thing I see is the the "Variables" tab is loaded with all of 
the script vars and their values.
- Debug is stopped at the 3 line of code. This is in the middle of a 
comment.
- I can now Step through the script.
- I can not select "run to next STOP". It will not detect the next 
manual STOP. It just runs to the end of the script.
- When I try to "Step Over" or "Step Into" the script the stepping is 
not from one line of code to the next all of the time. It is skipping 
lines of code. Like there is a sync problem between the real script and 
what Xdebug thinks the next line is.

--
Thanks in Advance...           http://weconsultants.prophp.org
IchBin, Pocono Lake, Pa, USA   http://ichbinquotations.awardspace.com
______________________________________________________________________
'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)