Previously, i was able to set up the php debugging using xdebug and eclipse(say box1). But on a new machine(say box2) this is not at all working. I have been through a lot of forums and threads but dint find the solution to resolve my problem. Detail of the problem is:
I am using :
eclipse helios 32 bit,
WAMP 32 bit,
on my 64 bit win7 box. (same setup on box1 except box1 has win8 64 bit). On box2, i have successfully configured the xdebug as everything seems ok on the phpinfo() page(compared with the one on box1). checked all the setting in php.ini on both boxes, no difference.
Now, i setup the Debug As configuration on box2 (similar as on box1) and when i choose to debug eclipse on box2, eclipse does not do anything, while on box1 it start the debugging and launch the application in browser.
May be i am making some silly mistake, coz i have setup this once before as mentioned on box1.
But this time i am not having any luck.
Can you guys help please? i have been stuck here for 3 days now. :(
let me know if you need any more info.
Thanks.
[Solved]
I have downloaded a new version of eclipse Luna for PHP from the official website, and things are working fine.
Not Sure what was wrong with the eclipse Helios but for now my trouble is over.
Happy PHP.
Thanks.
Related
I've been trying to get a php debugger for the last 2 days.
I ended up with xampp localhost-package and I'm pretty satisfied with it.
I just can't get any debugging to work.
Initially I tried to install xDebug, as was suggested here.
But that tutorial seems to be outdated. I tried couple other forum thread tutorials but couldn't get anything to work, with regards to xdebug. So abandoned xDebug and decided to stick with Zend because "it comes default" with xampp.
As far as I can tell, Zend Debugger doesn't come default with Xampp, I tried debugging with Eclipse, through my localhost server and it doesn't recognise the variables.
So I saw someone using a different version of Eclipse called "Zend Eclipse" and thought "surely that version has a default zend". I don't think it does, bugger if I know. I tried to "test" for zend debugger when creating a new debugging config and it says it's not installed.
Can anyone point me in the right direction of how to actually get Zend Debugger to run with Eclipse and Xampp?
Or..
Just tell me what you prefer to use for php debugging.
At this point, I don't care what I use, as long as it helps me debug my source code.
Thank you for your time.
Any help will be appreciated.
Regards,
James
I posted about this a week or so ago but since then I've done some further troubleshooting so I thought it was worth posting again:
I'm trying to set up PHP debugging in Komodo 7, using the Xdebug extension that ships with Komodo. The extension seems to be working fine, and Komodo responds when I try and start a debug session.
However, Komodo doesn't let me step-through my PHP code; instead it just runs through the code in a pane in the bottom-right of the Komodo window.
For the record, I don't have any Mapped URIs.
I'd really appreciate any help anyone's able to offer on this as I've got a website I need to debug for a great non-profit and this problem is preventing me from working.
Use the debugger connection preferences to change the port that Komodo listens to from the default value of 9000 to a system provided free port, 8080, or whatever port your remote host or localhost is running.
In the end I ran this past Activestate's tech support on IRC (#Komodo on irc.mozilla.org) who were really helpful. We couldn't work out what the problem was, though, so I ended up uninstalling XAMPP and Komodo, reinstalling both, and then following the instructions in the Komodo docs.
I'm currently running Komodo 7 and have XDebug set up on PHP 5.3.1, which is installed as part of XAMPP 1.7.3. All of this is running on Mac OS X 10.7.
Until I upgraded XAMPP (from version 1.0.1) step-through debugging of PHP in Komodo was working fine. I'd load a page in Firefox and the Komodo icon in the dock would start bouncing up and down, and I'd be able to step through my code, add breakpoints, etc.
It now seems that debugging isn't working properly. I'm confident that XDebug is set up properly, as it shows up when I run phpinfo(). However, when I load a page in Firefox, step-through debugging doesn't start in Komodo. Komodo does respond to an extent, in that information is displayed in the "Debug Output" pane in the bottom-right of the Komodo window, but there's no way I can see to start step-through debugging.
I've got a project I need to finish, so I'd really appreciate any help anyone is able to offer.
As per Hamish's comment above, this is indeed a duplicate (of sorts) of Can't get PHP debugging to work with Komodo (but I'm almost there!)
See that question for something approaching an answer.
I have installed NetBeans on Windows XP machine. I have also downloaded XDebug but I am not sure how to configure to debug the remote server(development machine). My development server is windows 2008 server(64 bit). What version of XDebug do I have to use? My local machine is Windows XP. I appreciate any suggestions.
I know it's far to late. But maybe the answer is helpful to someone passing by the post.
You can find customized installation steps here. The link provided is a reference to a page in which you paste in your php info. The page prints a list of steps to setup xdebug on your machine.
If the link is dead at the time of reading this post, please search using the keywords "xdebug tailored installation steps". This should take you directly to the page in question.
Hope this helps.
I'm having trouble with debugging a PHP project through NetBeans using XDebug, and was hoping someone out there might have had this problem before.
Debugging works fine for the requested php file - so if I go to index.php on the remote server, I can put a breakpoint anywhere in index.php in NetBeans and the code stops there and I can step through.
The trouble is, all the other files appear on the call stack like this: "file:///home/user/site_html/library/class.requestprocessor.php" and because that's a path to a file on the remote server, NetBeans is unable to resolve the name, and so I can't step through the code for it. It makes debugging practically useless! The php file that was requested, for example index.php, appears just as "index.php", it's just all the other ones which are included that NetBeans can't resolve properly.
Is there some setting in NetBeans or XDebug that I can use to solve this problem? I have tried my best looking through all the project settings and options in NetBeans, and also looked through all the configuration options of the XDebug extention, but to no avail. Surely someone out there must have had this problem before? How did you solve it? I'll be very grateful if you could let me know.
If there's no other way, do users of Eclipse PDT and XDebug have this problem when debugging on a remote server? If not I'll make the switch.
This issue appears to be fixed in NetBeans 6.7.
Okay it seems no one is going to answer the question, so I'll post the results of my research.
As I was unable to find a way to make NetBeans successfully debug as I wanted, I tried using Eclipse PDT and Visual Studio 2008 with the VS.php extension in order to solve my problem. Eclipse PDT was hell to setup, and I wasn't happy with the way you couldn't specify a port to use for your FTP server in its Remote Server Explorer. I found VS.php did everything I wanted, it automatically uploads the code, as well as having perfect debugging, and it was EASY to setup. The only thing is, it looks ugly and I can't find a way to customise its colours. However, I'm going to choose function over fashion, and so I've settled on using VS.php as my final solution. Which to be honest is a shame, NetBeans was really great, I just can't live without a working debugger.
I had this same issue. I'm running Netbeans 6.8. You have to right click on your project, go to project properties/run configuration/advanced and set up path mapping. Map the folder on the server to a folder locally so that Netbeans knows which files to open locally when it hits these methods.