Just like Node.js.
Running and debugging Node.js NodeJs Debugging
WebStorm supports the V8 Inspector Protocol, so you're good:
Go to "Debug Configurations" (Alt+Shift+9)
Add a configuration ("+" on top left corner)
Select "Attach to Node.js/Chrome"
Make sure the "Chrome" option is selected (should be default)
Click "Apply" and "Debug" to start the debugger
Create your breakpoints
With the debugger running, run your script with the --inspect-brk option:
deno run --inspect-brk -A app.ts
Now it will work as intended with the IDE. You can use the Debug view to step in, over, etc.
We should expect a plugin some time in the future.
From deno debugger:
Deno supports the V8 Inspector Protocol.
It's possible to debug Deno programs using Chrome Devtools or other clients that support the protocol (eg. VSCode).
You can run and debug files using Deno with the Deno plugin.
Related
I am using KDevelop version 5.4.2 in Ubunut 18.04. I want to use internal terminal, But there is no option of that.
In window-> Tool view, there is no option of terminal/ console
How can i add terminal in KDevelop along side with Code Browser and Build Windows at bottom of KDevelop layout.
Have installed angular CLI via node js command prompt. However, when I launch terminal in VS code, it doesn't allow to type only. PFA screenshot
PFB terminal setting screenshot
Able to run ng commands from node js command prompt outside vs code.
If your problem is not related to default shell in your terminal. Then you check windows settings. Follow the steps -
Open VSCode file location
Go to Compatibility tab in VSCode properties window
Unchecked Run this program in compatibility mode for: option
see the attached files. Try with this solution, it might help you.
This worked for me:
Remove settings file.
Click on view/terminal.
Select default shell.
I want to create a Go app with a console UI using the termui library (which is built on top of the termbox-go library). I can build the app and run it from the command line, but it will not start inside the GoLand IDE (2018.1.3) on Windows 10.
It fails during the termbox-go init when calling syscall.Syscall with SetConsoleScreenBufferSize parameter. The size for the screen buffer is 80x25. Error message is just "The parameter is incorrect."
How can I debug a termbox-go app in the GoLand or other IDE?
I think the way to solve this is to build your executable with Go 1.10 or newer, compile it with the following flags: -gcflags="all=-N -l" (these are very important and will allow the debugger to work a lot better, and then use the Run | Attach to Local Process... option from GoLand and attach to the local process.
I'll see if I can replicate the bug and update this accordingly.
I'm trying to debug a test using nosetests in PyCharm. I need to stop at a breakpoint and do some interactive debugging using the PyCharm debug console. However, whenever I type anything at the debug console prompt, nothing is printed; I just get a new prompt. The debug console works perfectly with pytest, but I need to use nosetests for this particular test. How can I get the console to work correctly?
Most likely your nose runner suppressing stdout. Try running nosetests with -s
Under the "Tools" menu, select "Edit Configurations." In the dialog, expand "Python tests" and select the nosetests you are running. Add "-s" as an "Additional Argument".
Under the Tools menu, select Edit Configurations. In the dialog, expand Python tests and select the nosetests you are running. On the Configuration tab, under the Nosetests section, make sure the checkbox in front of Params is checked and then add -s as a parameter to it. Apply and Save.
On my archlinux system I did a fresh installation of:
mono 3.0.7
monodevelop 4.0.8
monodevelop-debugger-gdb 4.0
When I debug an application the debugger doesn't stop on the breakpoints, even not on the System.Diagnostics.Debugger.Break (); code.
And an error windows is displayed with the following message :
Could not connect to the debugger
Does anyone know how to fix it?
This is due to a recent gnome-terminal change. Recent gnome-terminal no longer accepts the --disable-factory argument.
Install the xterm package, then in a gnome-terminal session do the following:
$ unset GNOME_DESKTOP_SESSION_ID
$ monodevelop
This will cause monodevelop to use xterm as its external terminal and all should be well.
As a workaround untick the "Run on external console" checkbox in your running project settings. You can find this option in the "Run" tab from the settings pane.
Another factor which will cause break points to not be hit is if you don't have "Emit debugging information" button set.
You'll find this setting in "Project" tab then at the bottom of the menu " Option". Then look for "Build" tree branch then "Compiler" option. The checkbox for "Emit debugging information" is here.
I had a similar problem - breakpoints was not triggered while checkbox "Use MSBuild build engine" was checked in the project properties.