If someone did want to write step by step instructions, how would they find out how to run it so they could write the documentation? Just trial by error or are there some cryptic notes somewhere so we can play around with it?
Right now, the only use of the debugger is for me is to reference to it on the menu.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's an attempt ;)
i) Download
- Download Dev-PHP version 2.0.13.261 or greater see below
- Download Xdebug windows modules http://www.xdebug.org/link.php?url=snaps-win
- Download / install the corresponding version of PHP
ii) Install PHP and Dev-PHP ;)
iii) Connect Dev-PHP and PHP
- Run Dev-PHP
- Create a new project (in short : a new directory)
- Create a new file 'index.php' containing
<?php
phpinfo();
?>
<omg>
there's a bug : the new file is hidden
Quit Dev-php, save the new file, Run Dev-PHP
Double-click on the filename in the list view
Here it is, add phpinfo();
</omg>
- Menu Option » General options...
- Select the third tab on the appearing window
- Fill the pathnames of php_cgi.exe and php.ini
- Select the fifth tab (Web-server)
- Check the port number of the local server (usually 8080) and the server timeout (usually 10000)
- Click on the Ok button
- Click on the second tab (Internal preview) of the main window of Dev-PHP
One should see the phpinfo results ;)
iv) Copy the file php_xdebug.dll in the "./ext" directory of PHP
v) Edit the PHP.ini
- Menu Options » General Options
- Select the last tab (Debugger)
- Click on the button 'Set debugger entries'
this will add a section called xdebug, initialized with the values set in the tab
don't modify the "idekey" option, because it's hard-coded at this time
- Click on the button 'Ok'
- Menu Options » Edit PHP.ini
- Set the key 'extension_dir', near line 500, for instance :
extension_dir = "C:\Program Files\dev-php2\php\ext\"
- Set the zend extension, near line 610, for instance :
zend_extension_ts="C:/Program Files/Dev-php2/php/ext/php_xdebug.dll"
- Save the file PHP.ini
- Click on the index.php tab
- Click on the internal preview tab
One should see the phpinfo results with something like
1) " with Xdebug v2.0.0beta6-dev, Copyright (c) 2002, 2003, 2004, 2005, by Derick Rethans"
just after the copyright of Zend Technologies
2) then, near the middle of the results, all the settings for Xdebug.
Hello, you say by Dev-php3-editor is debugging posible, so i can switch to php3-editor that's ok . But I have no Idea how to handle debugging. In the Forum I find entrys which must be set in the php.ini :
[debugger]
debugger.enabled = true
debugger.profiler_enabled = true
debugger.JIT_host = localhost
debugger.JIT_port = 7869
What are the next Steps ?
Thanks for any Idea for get running the Debugger dev3.0 By from Heidelberg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 2 has selected Xdebug.
AFAIK, Xdebug is a protocol, not really a debugger.
With Xdebug, one could choose a debugger.
These last weeks, i've built a new version (Exp) dealing with Xdebug.
Following features could be functional : Activate, Run, Run to cursor, Step into, Step out, Step Over, Stop.
To Do : Breakpoints, Context and modify, Evaluate, Profiling.
Alas, from now there are too many differences/conflicts with the current version on the svn server. :-(
w8 + c
Pierre.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
np
waiting for heidelberg's debugger ;)
working on the context button of dev-php's debugger : i think that a listview will be enought to store Fullname, Value and Address, may be Type...
To be continued.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i think that debugger interface is more stable
Todo : Context modify, Evaluate, Breakpoints.
This version is coming with some other stuffs :
- dockable Multi-Help treeview
- dockable Debugger-Context listview
- all dockable objects come with translucency
when undocked - but toolBars.
- listviews : revisited 'click on column header' event
- xaamp compatibility (see http://sf.net/forum/message.php?msg_id=3889985\)
- editable debugger toolbar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok all this is just great and fine. But how does one get the debugger to step thru code from a point you designate and show all the variable values as it does.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pierre those two links were already covered in the thread. Please read my second post of today. How does one step thru their code and watch variable change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First press "Activate" to start the debugger, *then press "Step into" at least once*. Then either you press "Step into" and "Step over" until you reach your point, or you set a Breakpoint (click in the margin) and press Run.
There is no automatic variable visualisation. To see the variables, you must press "Context". The variables display will keep their values until you press the "Context" button again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I actually meant that for davidof. Any help you could provide would be appreciated too piere.
I finally got xdebug to work in SOME *FREE* ide/editor. I have been trying for three years litterally. The step over and step out of buttons do not seem to work. And the variables display after clicking context does not scroll if you have the Dev-php window sized down too small but hey it does work. Just have to remember to constantly click the context button.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> The step over and step out of buttons do not seem to work.
I believe they work for me most of the times. I think there are reliability problems with the debugger, which can work then stop working without any reason I could find. Pierre, if you know of anything we could check to help pinpoint the problem... Or if you can show me where to start looking.
> And the variables display after clicking context does not scroll if you have the Dev-php window sized down too small but hey it does work. Just have to remember to constantly click the context button.
Yes, this is a bit annoying, but it probably has a positive consequence on performance during stepping, so I suggest we do a few tests and maybe find a way to make the automatic mode so that it is an option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pierre, don't bother answering my silly question: I found the answer my self. It took me one whole day to find the idea of searching for "xdebug" in the source :-D So now I ready to catch him "the hand in the bag" as John Wolf Whistle would say.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pierre, I am going to need logging to find this one. Is there a logging tool (apart from the rudimentary FTP Log) in DevPHP, or do you have anything to suggest?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
piere I only see the instructions page on that wiki link. But in answer to your question maybe you could go further then just installing and starting xdebug. Give some example code that can be copied and pasted. Something other then just a look where a variable is incremented. The go step by step thru the code in the wiki.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just had an issue I already met: I was debugging (I had set 2 breakpoints) when the debugger stopped responding. The debugging buttons were still activated but they failed to trigger anything. Everything else was ok, the IDE was responding correctly to my commands. I checked the debugger log file and I discovered that it wasn't changing any more. I guess the debugger was stuck or down and DevPHP wasn't aware of this, so it kept uselessly monitoring the file. I tried to kill the debugger, but pressing the Stop button didn't have any effect. I tried to switch to the Internal preview but I got in a seemingly endless exception loop, so I had to terminate Dev-PHP. Next time this happens, I'll check if the debugger process is still there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well I finally got the script I was working on debuged. Well sort of. Enough so that it actually does 99% of what I wanted it to do. I now need to just do some code cleanups. I will continue to work with Dev-PHP since its the only program that seems to have a working xdebug implementation.
The interfact to that can use a lot of work though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, where can I find a step by step Discription
for debugging for the (IDE basic 2.0.13.261 26-jul-2006)
Thanks a lot. from Heidelberg
bad - but you cannot find a step by step description!!
at this moment the better way for debugging with dev-php is using the new dev-php3-editor. debugging with version 2 is not stable :-(
when i have the time i will bring the debugger from version "editor(3)" to version "IDE(2)".
would be nice, i someone can write a howto for debugging with devphp-editor. thanks.
I would like to know the same as heidelberg.
If someone did want to write step by step instructions, how would they find out how to run it so they could write the documentation? Just trial by error or are there some cryptic notes somewhere so we can play around with it?
Right now, the only use of the debugger is for me is to reference to it on the menu.
Hello,
Here's an attempt ;)
i) Download
- Download Dev-PHP version 2.0.13.261 or greater see below
- Download Xdebug windows modules
http://www.xdebug.org/link.php?url=snaps-win
- Download / install the corresponding version of PHP
ii) Install PHP and Dev-PHP ;)
iii) Connect Dev-PHP and PHP
- Run Dev-PHP
- Create a new project (in short : a new directory)
- Create a new file 'index.php' containing
<?php
phpinfo();
?>
<omg>
there's a bug : the new file is hidden
Quit Dev-php, save the new file, Run Dev-PHP
Double-click on the filename in the list view
Here it is, add phpinfo();
</omg>
- Menu Option » General options...
- Select the third tab on the appearing window
- Fill the pathnames of php_cgi.exe and php.ini
- Select the fifth tab (Web-server)
- Check the port number of the local server (usually 8080) and the server timeout (usually 10000)
- Click on the Ok button
- Click on the second tab (Internal preview) of the main window of Dev-PHP
One should see the phpinfo results ;)
iv) Copy the file php_xdebug.dll in the "./ext" directory of PHP
v) Edit the PHP.ini
- Menu Options » General Options
- Select the last tab (Debugger)
- Click on the button 'Set debugger entries'
this will add a section called xdebug, initialized with the values set in the tab
don't modify the "idekey" option, because it's hard-coded at this time
- Click on the button 'Ok'
- Menu Options » Edit PHP.ini
- Set the key 'extension_dir', near line 500, for instance :
extension_dir = "C:\Program Files\dev-php2\php\ext\"
- Set the zend extension, near line 610, for instance :
zend_extension_ts="C:/Program Files/Dev-php2/php/ext/php_xdebug.dll"
- Save the file PHP.ini
- Click on the index.php tab
- Click on the internal preview tab
One should see the phpinfo results with something like
1) " with Xdebug v2.0.0beta6-dev, Copyright (c) 2002, 2003, 2004, 2005, by Derick Rethans"
just after the copyright of Zend Technologies
2) then, near the middle of the results, all the settings for Xdebug.
vi) Feel free to check the last Exp version (1.38MB)
http://devphp.sf.net/2.0/devphp2.exe
Best regards,
Pierre.
Hello, you say by Dev-php3-editor is debugging posible, so i can switch to php3-editor that's ok . But I have no Idea how to handle debugging. In the Forum I find entrys which must be set in the php.ini :
[debugger]
debugger.enabled = true
debugger.profiler_enabled = true
debugger.JIT_host = localhost
debugger.JIT_port = 7869
What are the next Steps ?
Thanks for any Idea for get running the Debugger dev3.0 By from Heidelberg
Version 2 has selected Xdebug.
AFAIK, Xdebug is a protocol, not really a debugger.
With Xdebug, one could choose a debugger.
These last weeks, i've built a new version (Exp) dealing with Xdebug.
Following features could be functional : Activate, Run, Run to cursor, Step into, Step out, Step Over, Stop.
To Do : Breakpoints, Context and modify, Evaluate, Profiling.
Alas, from now there are too many differences/conflicts with the current version on the svn server. :-(
w8 + c
Pierre.
Hello Pierre,
Super :-)))))))
Thank you veryyyy much
for this super description.
Wenn I Testet the description, I give a Feedback.
you spend so much time, ... Thank you veryyyy much :-))))
By from Heidelberg
yes really great pierre!!!
thousand thanks also from me.
this days i have only a small, small time to work for dev-php... :-((((
np
waiting for heidelberg's debugger ;)
working on the context button of dev-php's debugger : i think that a listview will be enought to store Fullname, Value and Address, may be Type...
To be continued.
Hi,
New bugs to hunt inside the last version 2.0.13 ;)
http://devphp.sf.net/2.0/devphp2.exe
i think that debugger interface is more stable
Todo : Context modify, Evaluate, Breakpoints.
This version is coming with some other stuffs :
- dockable Multi-Help treeview
- dockable Debugger-Context listview
- all dockable objects come with translucency
when undocked - but toolBars.
- listviews : revisited 'click on column header' event
- xaamp compatibility (see http://sf.net/forum/message.php?msg_id=3889985\)
- editable debugger toolbar
Ok all this is just great and fine. But how does one get the debugger to step thru code from a point you designate and show all the variable values as it does.
see http://sourceforge.net/forum/message.php?msg_id=3889975
and http://pierre.fauconnier.free.fr/wikini/wakka.php?wiki=DevphpEnXdebug
Pierre those two links were already covered in the thread. Please read my second post of today. How does one step thru their code and watch variable change.
shaba1,
First press "Activate" to start the debugger, *then press "Step into" at least once*. Then either you press "Step into" and "Step over" until you reach your point, or you set a Breakpoint (click in the margin) and press Run.
There is no automatic variable visualisation. To see the variables, you must press "Context". The variables display will keep their values until you press the "Context" button again.
Ok that did it. Thanks Pierre. I would like to keep in touch in case I had other question
> I would like to keep in touch in case I had other question
No problem, you're welcome.
Also, davitof is pretty accurate.
I actually meant that for davidof. Any help you could provide would be appreciated too piere.
I finally got xdebug to work in SOME *FREE* ide/editor. I have been trying for three years litterally. The step over and step out of buttons do not seem to work. And the variables display after clicking context does not scroll if you have the Dev-php window sized down too small but hey it does work. Just have to remember to constantly click the context button.
> I have been trying for three years litterally.
According to you, how should we improve the wiki ?
http://pierre.fauconnier.free.fr/wikini/wakka.php?wiki=DevphpEnXdebug
> The step over and step out of buttons do not seem to work.
Could you file a "Tracker » Bugs" ?
> the variables display after clicking context does not scroll
> if you have the Dev-php window sized down too small
Same as above.
> Just have to remember to constantly click the context button
Could you file a "Tracker » Feature request" ?
Thanks for your report,
Pierre.
> The step over and step out of buttons do not seem to work.
I believe they work for me most of the times. I think there are reliability problems with the debugger, which can work then stop working without any reason I could find. Pierre, if you know of anything we could check to help pinpoint the problem... Or if you can show me where to start looking.
> And the variables display after clicking context does not scroll if you have the Dev-php window sized down too small but hey it does work. Just have to remember to constantly click the context button.
Yes, this is a bit annoying, but it probably has a positive consequence on performance during stepping, so I suggest we do a few tests and maybe find a way to make the automatic mode so that it is an option.
Pierre, don't bother answering my silly question: I found the answer my self. It took me one whole day to find the idea of searching for "xdebug" in the source :-D So now I ready to catch him "the hand in the bag" as John Wolf Whistle would say.
Pierre, I am going to need logging to find this one. Is there a logging tool (apart from the rudimentary FTP Log) in DevPHP, or do you have anything to suggest?
piere I only see the instructions page on that wiki link. But in answer to your question maybe you could go further then just installing and starting xdebug. Give some example code that can be copied and pasted. Something other then just a look where a variable is incremented. The go step by step thru the code in the wiki.
I just had an issue I already met: I was debugging (I had set 2 breakpoints) when the debugger stopped responding. The debugging buttons were still activated but they failed to trigger anything. Everything else was ok, the IDE was responding correctly to my commands. I checked the debugger log file and I discovered that it wasn't changing any more. I guess the debugger was stuck or down and DevPHP wasn't aware of this, so it kept uselessly monitoring the file. I tried to kill the debugger, but pressing the Stop button didn't have any effect. I tried to switch to the Internal preview but I got in a seemingly endless exception loop, so I had to terminate Dev-PHP. Next time this happens, I'll check if the debugger process is still there.
Well I finally got the script I was working on debuged. Well sort of. Enough so that it actually does 99% of what I wanted it to do. I now need to just do some code cleanups. I will continue to work with Dev-PHP since its the only program that seems to have a working xdebug implementation.
The interfact to that can use a lot of work though.