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.
Related
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.
I have Visual Studio Code version 1.22.2 running on Windows. When working on Javascript code, it crashes and causes a blue screen with the following technical info:
STOP: 0X0000007E
mfeavfk.sys - Address <...>
I have a plugin for MS SQL and a beautify plugin installed.
I recently updated Windows and started experiencing BSODs every time I started VS Code. Here's how I fixed it - hopefully this helps someone else:
Open a command prompt and type the following command:
code --disable-extensions
If your computer doesn't BSOD after this step, then an extension is likely causing the issue.
Press ctrl+shift+x to open the extensions sidebar
Under disabled, uninstall any extensions you aren't using or don't recognize.
Restart VS Code, and see if it still crashes.
If step 3 didn't help, try removing all extensions and then reinstalling one at a time until you find one that causes the crash. Then repeat steps 1-4, this time removing the extension you identified as causing the crash.
After upgrading to Python 3.6, Eclipse debug mode stopped working properly. It renders an error like this:
The strangest thing is that this issue does not raise in 100% of cases. Sometimes it goes away. And then again arises. I am lost trying to figure out why.
Although it happens when you're running the PyDev debugger, the debugger is probably only exercising some path in your code which has a bug and is usually not exercised (and thus leads to such an error).
In this case, attach a c/c++ debugger to the program to find the culprit (you can use the attach to after that error is hit)... On Windows you can use Visual C++ and on Linux GDB.
-- as a note, the issue is probably on some c/c++ library you're using (but given the info, it's really hard to pinpoint anything).
I'm following these instructions to remotely debug a python script http://pydev.org/manual_adv_remote_debugger.html
Using breakpoints and stepping work without a problem, but after resuming the script (without any other further breakpoints) the script executes the remaining instructions, and then hangs instead of exiting normally. Even closing the server from pydev does not help, I have to Ctrl+Break the script
I am sure I've done this a while ago with an older eclipse+pydev, and the script resumed and exited normally (and it's very important for me not to mess the rest of the execution).
I've tried this with both Eclipse Luna and Liclipse pydev_4.0.0.201504132356, pydev_4.0.0.201504092214 on Windows 7 x64, same behaviour
Is this an intended behavior or a bug? How could I make pydev let the script end normally?
I can't reproduce this here... please report that as a bug adding details on how to reproduce it (i.e.: ideally, create a project on github and add a step-by-step on how to reproduce it so that it can be fixed... without being able to reproduce it properly, it may be pretty hard to fix).
Also, please give details on the OS and Python version used in the report (https://sw-brainwy.rhcloud.com/tracker/PyDev/)
This should be quite a popular problem but neither Google nor stackoverlow search helped my with it.
I want to develop Python3 programs in Netbeans 6.9.1. But when I create project, toggle a breakpoint and press on the Debug button I see following output:
[LOG]PythonDebugger : overall Starting
[LOG]PythonDebugger.taskStarted : I am Starting a new Debugging Session ...
[LOG]This window is an interactive debugging context aware Python Shell
[LOG]where you can enter python console commands while debugging
>>> File "/home/proger/.netbeans/6.9/config/nbPython/debug/nbpythondebug/jpydaemon.py", line 219
print self.debuggerFName
^
SyntaxError: invalid syntax
Debug session Abort =1
>>>
And below the log window I see:
ERROR::Server Socket listen for debuggee has timed out(more than 20 seconds wait) java.net.SocketTimeoutException: Accept timed out
So if I understand it right Netbeans tries to debug Python3 code with Jython2.something debugger. Is there a way to attach right debugger?
I met the same problem when using NetBeans. I solved this problem by editing the jpydaemon.py
change the code about 219 line
print self.debuggerFName
==>
print(self.debuggerFName)
Restart NetBeans, and it works.
I don't know how Netbeans work, but from the error message it looks like the Python 3 interpreter gets fed Python 2 code. I would venture that Netbeans hooks a debug server into Python via a breakpoint hook, so when a breakpoint is reached it starts a debugging server that the netbeans IDE then tries to talk to.
This debugserver (jpydaemon.py) evidently has not been ported to Python 3, at least not in your version.
I doubt anything is being executed by Jython. The code in this case seems to be written for Jython as it's called jpydaemon.py, and in any case Jython doesn't support the Python 3 syntax yet, so if you are trying to develop Python 3 code and run it with Jython you are likely to fail quite miserably. :-)
Update: after looking at jpydaemon.py I conclude that I guessed exactly correctly. jpydaemon contains the debugger serveice, which is hooked into the debugging hooks via sys.settrace(). So the problem you are having is quite simple: jpydaemon.py is not ported to Python 3 yet, so you can't use Netbeans internal debugger to debug Python 3 code.