Closed nbyloff closed 8 years ago
Sorry, I am going to close this issue. It was a dumb mistake on my part, but I just had to write it out to see it. I shouldn't map on the public folder, but the root project folder.
Maybe this will help someone in the future double checking their config. Everything above is correct, except I just had to delete the public folder on both ends in the path_mapping
However it does work when I use the
xdebug_break;
in my code, or put a breakpoint in the index.php file (testing on laravel homestead).My setup:
There is no error or issues reported in the Sublime-Console.
This is my project file. Triple checked the path mapping: essentially navigated to the folders on each machine and pasted in their paths.
Here's my xdebug.ini file on the vagrant machine
Here is my XDebug sublime user settings
I am using the Chrome XDebug plugin. I enable the plugin in the browser and hit CTRL + SHIFT + F9. I refresh a page, and the log file in /tmp/xdebug.log shows it's connected, and even lists off the break points I have configured, but it doesn't stop.
And again, if I put the break point in index.php instead of the controller, it stops just fine. If I put the
xdebug_break;
in my controller method, it breaks (don't see the yellow dot though). Also, if I setbreak_on_start
to true, it will halt as well. But I can't set my own break points or step through and follow the dot.Here is a sample log entry of it connecting, but it's loading a page where there's a break point in the controller, but it doesn't stop. Noticed the first line references
XDEBUG_ECLIPSE
even though I set my idekey. Not sure if that's a big deal, but again, it connects to Sublime Text just fine.