Visual Studio Code (VSC) when hitting F5 to start the debugger, it spawn a page localhost:53519 which is does not make any sense to me. It does not affect the debugging function, it is just that it is there and I have to click to close it.
I cannot find that port number in "Open Configuration".
I did not expect this page to be launched when F5 is executed.
Update: Debugging php with xdebug installed. Live server was previously installed but later removed, and the problem is still there.
Related
I'm developing an office-js taskpane add-in for Excel.
I am using VS code as the IDE and debugging environment.
After running a debug, more often than not I cannot run a second debugging session because VS code does not launch WebPack.
I end each debugging session simply by closing Excel. That also ends the session according to the VS code terminal. But if I hit F5 again, Excel starts immediately and webpack does not. I have to reboot the machine to get it working again.
Does anyone here know how I might fix this extremely annoying issue?
Here are a few links you may find helpful in debugging Office Add-ins:
Debug Office Add-ins
Attach a debugger from the task pane
Sideloading and Debugging Outlook Add-ins
I have a really wired problem (or a bug) on vscode. I can "attach chrome" debugging totally fine usually,
but after some random time connecting to the chrome instance (may be a couple of hours or 8 hours, like I left it connected while I'm sleeping), it automatically disconnect the debugging,
then when I try to re-run attach chrome to reconnect it, for some weird reason it doesn't connect to the instance.
It's not a failed, it's not like "cannot connect to the port 9222", it's infinitely trying to connect showing the left up side blue indicator left to right.
This is my second time to encounter this weird problem. For the first time I even don't know how I solved the issue. maybe I just waited its reconnect for an hour or like that.
The first things I happened to think from the problem is simply its port conflict. So I checked vscode side's (I mean I use vscode in the remote ssh mode from Windows to Linux Ubuntu) port and process, used htop to filter port "9222" or process "chrome", but I didn't find anything stucking there. So I assume in the linux side the debugging process is exiting successfully.
So I did the same on the Windows side, I used resource monitor to check port "9222", no running process. If I re-open a 9222 debugging enable chrome, then it appears. closing, it disappears. It seems there is no problem here as well.
I then checked vscode's version. I was using vscode 1.64.2 so I side-installed 1.65.2 and 1.66.1 (the latest) and tested it. Doesn't work.
"refreshing the window" doesn't work. closing the window and re-open, doesn't work.
So what can I do?
Did you just install some new extensions in Visual Studio Code? I found that I had this exact same behaviour, "infinitely trying to connect showing the left up side blue indicator left to right", after I installed Karma Test Explorer and Test Explorer UI extensions. Once I uninstalled those extensions, debugging started working again.
I'm using XDebug with Visual Studio Code on Windows 10 to debug PHP.
The debugger works but from time to time it's getting stuck (hits the breakpoint but doesn't respond to step in, step over commands).
I tried switching to XDebug nts version (Not Thread Safe) but it doesn't help. Restarting the web server (Apache) doesn't resolve it either. Sometimes computer restart helps but not always...
Any solution or workaround? (Even a command line that frees this deadlock)
Having out of context debug expressions in the watch window causing the debugger to get stuck.You should clear the watch window from expressions.I guess the evaluation of out of context expressions make the debugger to get stuck.
I am trying to setup XDebug for my CakePHP application. Here is my system info:
Using WAMP (Windows 10, Apache 2.4.23, MySQL 5.7.14, PHP 5.6.25)
CakePHP v3.4
Netbeans v8.2
I then click the Debug Project option, under the Debug Menu. This will start a new browser window, with this URL: http://localhost/MyCakePHPApp/?XDEBUG_SESSION_START=netbeans-xdebug
Then the browser will just keep spinning. In the bottom of the browser, it says "Waiting for localhost..." It will continue to do this until I hit the NetBeans Continue button, twice. Then the app will load properly. It's almost like there is a break point somewhere, even though I cannot see it. in my breakpoint window, I can see that there are no breakpoints set. Also, if I add a breakpoint to my code, it also never gets hit.
I use the combination of Eclipse PDT and XDebug very successfully to develop and debug my applications. So thanks to their creators, and if you haven't tried this combination, I strongly suggest you do.
The only thing bugging me is, that I couldn't find a way to start a debug session by requesting a random script right in my browser. I always have to start the session in Eclipse on one of my scripts and debug configurations.
I have minimized the pain by adding a "debug.php" to my project that contains only
<?php
// you can debug any request now
but still I have to finish this script and then do the request to whatever I really want to debug.
Is there a way to create a debug configuration that is not bound to a specific script but just tells PDT to start listening for requests from XDebug?
Go to preferences panel and select php->debug->installed debuggers and click on xdebug then click on configure. There should be an option to allow incoming connections. Select that and you can launch remote debug sessions from firefox with the xdebug extension