I am running Homestead on Windows 10 machine with Virtual Box. I have VSCode running on the Windows machine and I want to be able to debug code in the VM.
I have followed this setup:
https://tighten.co/blog/debugging-configure-xdebug-and-laravel-homestead-and-vs-code-and-phpunit
Once I am listening for Xdebug I run my code in the VM using phpunit test/Feature/AdminTest.php and this fails with
Unable to open 'BaseTestRunner.php': File not found
(file:///c:/g/Sites/Laravel/everyone-in-mind/vendor/phpunit/phpunit/src/Runner/BaseTestRunner.php).
Which is obviously showing me the Windows path.
If I stop the debugger and run again the test runs fine.
Do I need to install something extra to get BaseTestRunner?
When you are debuging a PHPUnittest with xDebug in VSCode with the PHPUnit plugin from Elon Mallin, check that you have disable the option Breakpoints/Everything.
It seems as if PHPUnittest, running from the PHPUnit-plugin, could not find the BaseTestRunner.php file and raised an exection. When you ignore this exception, you can run and debug your test.
see the same question PHpUnit with xdebug Breaks at BaseTestRunner instead of the actual test
It works for me and can now debug the Unittest.
I'm running Eclipse 4.6.1 with in-IDE Tomcat 8.5.6 on Windows 10 Professional 64-bit Anniversary Edition.
After Tomcat is left running in Eclipse after some time, the Tomcat embedded in Eclipse can no longer be stopped. I press the red "Stop" button in the "Servers" tab, but nothing happens. Eventually Eclipse will ask me if I want to terminate Tomcat:
Server Tomcat v8.5 Server at localhost is not responding. Do you want to terminate this server? Click OK to terminate the server or click Cancel to continue waiting.
I click "OK to terminate the server... but Tomcat keeps running.
Unfortunately when I then try to close Eclipse, it hangs on "Saving workbench state." Finally I have to kill Eclipse, thereby losing my workbench state. Even worse, if I then start Eclipse back up and try to restart the embedded Tomcat, I get the following error:
'Starting Tomcat v8.5 Server at localhost' has encountered a problem.
Several ports (8005, 8080, 8009) required by Tomcat v8.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).
How can I surgically go in and really kill Tomcat so that it doesn't hang Eclipse and keep ports open? (Unfortunately the only thing that shows up in the task manager is Eclipse.exe. There is no Tomcat to be seen. I've tried killing the javaw.exe subprocess, but that doesn't help.)
(At one point I thought this was related to a VPN connection going down, but today this happened with no VPN connection at all.)
I've filed Eclipse Bug 511342. We'll see if anything comes of it.
i've tried locally but i couldn't recreate the bug .
im not sure that this answers your question but it is for sure something worth trying , in any case this might show some features to other users....
in the window menu you have the SHOW VIEW , there you can choose other
this open the future window with search bar and all the available views for the ide .
in the debug view , you can do actions not only on applications , but on servers also . the menu here is different from the view you see in the server, and you can do advanced termination other things.
welp , hope that helps .
*note , you don't need the server to run in debug mode .
Find your Tomcat installation directory, navigate to bin folder, open a command window there and execute an .bat file named shutdown.bat, this way you can kill tomcat directly, make sure to locate the appropiate Tomcat installation directory which Eclipse is using.
UPDATE - Expected output:
I have not used it in the same way you have, but this may help.
On a command prompt (Cmd.exe) execute:
netstat -a -o | find "8080"
That will list all IP/PORT in use alongside the PID (process id) filtering by port # 8080 (change it to meet your needs or remove the find if you want to list all)
Open Task Manager, and using the PID you should be able to find the particular
process that is using the ports you need to release.
updated:
Once you find the port (8080) you can try using the command
taskkill /f /pid [port number]
Found a related issue with this command: Stack overflow - Tomcat not shutting down eclipse
Again, I use this when I need to find a rogue thing that I need to kill, and I don't know if the embedded environment will show it separate but its worth a try.
In tomcat's console inside Eclipse, there's a red button that can stop it. Albert also stated that in task manager it appears as javaw.exe, however Eclipse itself also appears as javaw.exe, so be careful when killing each one. Eclipse should be the one that takes more memory.
I've switched from Eclipse to PHPStorm and everything is working fine but only the debugging with XDebug ans SoapUI is still not working.
XDebug is installed. I used to add a GET parameter ?XDEBUG_SESSION_START=ECLIPSE_DBGP on the end of the wsdl url in SoapUI and Eclipse stopped at the first breakpoint properly.
When I close Eclipse, start PHPStorm and click to start listening for debug connections nothing happens.
I use ?XDEBUG_SESSION_START=PHPSTORM_DBGP. Only a Chrome-Plugin is able to start debugging in PHPStorm, but I need to debug with SoapUI too.
Can anyone help me with this issue?
Thank you very much in advance for any help!
I had to set path settings at PHP Servers configuration.
When I do on my app.js Debug As > Node Application it says
Launching STANDALONE_V8 has encountered a problem.
Failed to connect to Standalone V8 VM
connect timed out
It should start an app. Doing so directly on my terminal works fine.
When I start a debug session in my terminal and than try to debug it in Eclipse works fine too.
So is there anything that has to be done in order to make it work in Eclipse?
What exact error is in ErrorLog View on in Nodeclipse Console?
What is Java is used and Nodeclipse version?
Try to specify Java version: in eclipse.ini point to JDK 7
Check also
- toggleBreakpointsTargetFactory specified id is already registered
I have am trying to debug some PHPunit tests in netbeans, but it doesn't stop at my break-points.
I can, however, debug the site in the browser and it stops at my breakpoints.
I have modified file->project properties->run configuration->advanced to "do not open web browser".
I use the following script to initiate phpunit :
export XDEBUG_CONFIG="idekey=netbeans-xdebug";
phpunit $#
What could be the problem?
ps. I have had it working in the past, but it stopped working and I had to reinstall xdebug. I am using ubuntu 11.10
Thanks.
This usually happens when your port is not set to listen on xdebug's default listener port 9000.
Here's some instructions on mac for netbeans but it should do the trick even if you're running windows.
http://netbeans.org/kb/docs/php/configure-php-environment-mac-os.html