I'm able to debug Deno code in both VSCode and Rider, however, the debugger continues running even after the program terminates. I tested with a single line program, console.log('hello'), and it still had the problem. When it ends, you have to remember to stop the debugger.
Is this a bug?
Related
If I set a breakpoint (Visual Studio Code) somewhere in my code and then run the app with debug, the bebugger always stops on event_bus.dart respectively on the line with streamController.add(event);
If I then continue the program, it runs normally without ever stopping at my set breakpoints.
I'm having an issue when debugging c++ programs in emacs (using dap-mode, LSP, projectile...):
I have no problem with the debugger, as long as my code doesn't crash. But when the debugger hits a segmentation fault, I get the usual messages that I would see in gdb for instance, but then I also get this line:
Stopping due to fatal error: NotImplementedException: No handler implemented for request type: 'ExceptionInfoRequest'!
Then emacs freezes and the only way to unfreeze it is to kill clangd. however, when I get back control over emacs, LSP detects that clangd crashed, and suggests I restart the server. Even if I say no, emacs hangs again and I can only kill emacs to close it.
I am fairly new to emacs, and just discovered LSP / DAP integration, so I apologize if I missed anything obvious during the setup process. I don't know how to get further information on this error, I am not sure if the problem is in the vscode-cpptools, in clangd, emacs, or in the dap-mode package.
Has anyone encountered the issue, or knows how to fix this?
Even though I have set below code in setting.json:
"terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe"
Whenever I open the "integrated terminal" it starts and right away shows:
"The terminal process terminated with exit code: 259"
There is also a dialog outside code saying:
"powershell has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available."
this happens in 32bit and 64bit too
Any idea how to overcome this?
The code 259 usually means STILL_ACTIVE and this is rather strange.
You may try to use ProcessMonitor to determine which processes are started during your call and perhaps that gives you a clue.
Open Task Manager
I Clicked on End Task on all process of VS Code
Error vanished
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.
Is there a command line console that I can try and execute lines of code in Unity?
Something like the Chrome console for javascript, or running python on the command line?
I am on windows 8.
I saw the immediate window in MonoDevelop, but it didn't seem to work without a debug session, and when I was debugging it said it wouldn't run when the application was running:
> this
The expression can't be evaluated while the application is running.
> this
Debug session not started.
It probably wanted to be at a breakpoint, which was not obvious to get working and kept crashing when I tried various ideas. I would rather just use the console independently from debugging - just to experiment with syntax etc.
What is the easiest way to bring up a console for executing lines of C# unity code?