[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.php] Re: Problems with PDT and Xdebug

Dave Kelsey wrote:
See embedded comments

Dave Kelsey

IchBin wrote:

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.
Don't know why eclipse has decided to not allow you to have an internal browser. Linux
is problematic with this, but windows seems to be ok with this.



It looks like only when doing PHP debugging it will not let you use an internal browser. Sometime back using the Zend debugger it let you use an internal browser when debugging.


I do not want to run the Zend debugger because it is not *open source*. Not sure why the heads at Eclipse is letting this happen.


- 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.

This issue is described in the provided documentation.

Sorry, this may be my own expectation problem. I have used eclipse for Java and it's debugger for three years now. I need to revisit your PDF.


Just to let you know the "pathmapper version" distribution is different than yours. That is, is more like the normal install. The zip file has the dir structure so unzip can zip into the correct subdirectory. Also it does not redistribute your PDF file.

But the bad thing is that the libs do not conform to the eclipse naming convention. It was scary and I think it will cause confusion in the future. That is, the "pathmapper version" has this convention:

<DIR> features
  org.eclipse.php.xdebug_0.1.3.logik.jar
<DIR> plugins
  org.eclipse.php.xdebug.core_0.1.3.logik.jar
  org.eclipse.php.xdebug.logik_0.1.3.logik.jar
  org.eclipse.php.xdebug.ui_0.1.3.logik.jar


- 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.

"run to next STOP" is not something I am familiar with in PDT. Which version

On the PHP Debugger Perspective its the button to the left of the "Step into" button. I am using pdt-all-in-one-S20070130_RC2-win32.


are you using ? I have not looked at the latest integration level. If you have
a break point defined and you execute (ie F8) do you stop at the defined break point ?

No it does not stop and runs to the end and displays output in external browser..


if not, does your apache server have the htdocs set to your workspace ?

no.. I have the URL pointing to the code that is under my general documentroot. Sorry maybe they are out of sync. I will check.


Having to start apache and pass the documentroot of the Eclipse project it a problem. There has to be a better way. A open source php debugger called twWebEditor does not require this.

Would it be better to just define multiple eclipse php projects within the Apache config?

I know there is a pathmapper version as well on bugzilla, but I am not familiar with the changes
in that version as they were provided by someone else, are you using the pathmapper

Yes, I am using "pathmapper version" because that seemed to be the latest. So, anyone can contribute to the Xdebugger project with out project consultation? If so this would seem to be dangerous. I realize you started this Xdebugger project and I am more than thankful. For QA purposes this seems to be dangerous.


version and trying to map the paths from the workspace to the version running on apache ?

- 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.


If you have embedded php code within an html page, I have seen similar results
with xdebug. This could be due to the way php converts non php script code into
echo statements. What version of xdebug are you using ?

This was not doing this when I used the Zend debugger. This does not presently happen with tsWebEditor or PHPedit which have Xdebug implemented.


Dave, as mentioned in the start of this thread this is what I have installed.

 - pdt-all-in-one-S20070130_RC2-win32
 - Prebuilt Binary of XDebug With Path Mapper V0.1.3 (PDT RC2)
    [org.eclipse.php.xdebug.y.updatesite.zip]
 - php 5.2.1-dev
 - php_xdebug-2.0.0rc3-5.2.1

Hope I answered all the questions.

--
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-)