I am currently trying to get Xdebug to work on our development server. As client I am using netbeans and the connection so far works without problems.
But when I try to set a breakpoint within netbeans it is just getting ignored.

And yeah, I already googled for hours and also found some questions here that perfectly fit my description:
SO 1SO 2

But this does not seem to solve it for me. The Xdebug module is loaded via zend_extension=path/to/xdebug. so in the

/etc/php5/conf.d/xdebug.ini

I also looked at the php5/apache and php5/cli php.ini to make sure it is not loaded with extension= somewhere there. I also checked the "additional .ini files parsed" found by phpinfo() and it seems to be nowhere else loaded.

By executing php -m I can see the loaded Xdebug module in

[PHP Modules]

and in

[Zend Modules]

Not sure if this indicates that it is still loaded twice or if it is fine like that? Still if I remove the zend_extension=/path/to/xdebug.so from the conf.d/xdebug.ini it is also no longer loaded. So I really assume it is only loaded there.

If I set the remote_log option is see that Netbeans is trying to set something:

Seems suspicious that it appears in PHP Modules and Zend Modules, but I don't have any idea how that could happen. Have you tried the "Tailored Installation Instructions" at xdebug.org/find-binary.php ?
– mjsAug 6 '10 at 21:34

Hi, sorry for the late response was away over the weekend and i am not back at office before wednesday. But then i'll give it a try, thanks.
– enricogAug 9 '10 at 9:57

Hi, just tried the Tailored Installation Instructions, but didn't change anything. Actually i think it is pretty much the same like what pecl install is doing. It also told me "You're already running the latest Xdebug version".
– enricogAug 11 '10 at 11:23

I noticed that the path for the breakpoint was all wrong. It turned out that I had to setup Port Mapping in Eclipse. After setting the correct mapping the breakpoints started working. Also my remote_log now shows the correct path:

Thanks! That really pointed me into the right direction. Problem was with path mapping. Seems you have to map all the needed folders, not only parent folders, also see : wiki.netbeans.org/…
– enricogFeb 14 '11 at 9:25

Tough i wasn't able to test mapping for all folders right now, Netbeans seems to have a bug so I'm currently unable to add/edit the Server Path. Tough it looks like that should be useful if somebody else steps over this problem. For me it now strangely works also without any mapping. So thanks a lot again for pointing me in the right direction ;)
– enricogFeb 14 '11 at 9:29

Thanks! Although I stumbled over "Port mapping". Should be "Path mapping", right?
– Frank HintschJan 16 '17 at 11:29

+1 for the image (it made re realize I had recently reinstalled WAMP and forgot to change this again) If you are using WAMP, go into your php.ini from the WAMP icon and change the line to "xdebug.remote_enable = on" (from 'off')
– BillyNairSep 28 '15 at 16:03

xdebug would continuously wait on the session but after setting the remote debug flag the session wait issue, breaking point issue as well the xdebug log file that I had defined also started logging transactions.

Yet another possible solution, the only one that worked for me, after trying everything in this post and in many others...

I'm debugging a PHP project through XDEBUG on Eclipse Neon on Windows. The source is remote Linux, mounted locally as a drive through SFTP. It's probably my own fault that this isn't set up correctly...

In Eclipse, right-click your project, then select Configure, then Add PHP Support. Immediately, the DLTK indexing started; before that it wouldn't start no matter what.

Then I had to open my source and set the breakpoints through Remote File Explorer. I hope this helps someone.

Solved!
When creating a new project in NetBeans, I first set the root folder of the project to the WordPress theme folder of my WordPress site.
So instead, I created a new project with the root of it being the root of the entire WordPress site rather than just its theme, and the breakpoints started to work. Woohoo!