When I attach to my proccess via vscode debug It just stuck and I can not to terminate it, can not to reload it / pause / stop, everything. The breakpoints is not working, the debug will not stop on a breakpoint when should...
I can't start another debug process, can't attach to another one. It's just stuck and I have only one option - close vsCode
The problem is only with attach proccess in debug. Everything else working fine...
Buttons aren't working, nothing happens while I turn off vsCode completely
Tried to change variables in launch.json etc. Nothing changes
All worked fine in evening last month, next day the debugger is dead like that.
My launch.json setting for attaching
Related
Every time I open VSCode I see this .vscode/setting.json. i tried deleting it but I don't know how to make it go away for good
I tried to delete it but it kept appearing in my window.
I'm new to VS Code, and is following the official tutorial to learn how to debug. However, it just won't work. First, the UI looks different. It shows "RUN".
Compared to what the UI looks like in the video, which shows "DEBUG".
Also, I added a breakpoint and hit the green start button, it just never stops.
Here's the launch.json file:
What should I do to make the debugger work?
You need to run node in inspect mode.
In terminal / console, do:
node --inspect app.js
I'm trying to assign Cmd+R to Debug/Start Debugging on Vscode (1.33.1).
Cmd+R had an initial assignment to Reload Window so I removed it. Then when I pressed Cmd+R it started waiting for the second keystore. I went to keyboard shortcuts again and removed all two-key occurances that were present (that were causing a wait for a second keypress after R).
Now when hit Cmd+R, I see the Debug / Start Debugging highlight briefly on menu bar, which means that the menu item is invoked:
However, nothing happens. It doesn't start debugging (nor waits for a second keypress) When I manually click the same command, it starts perfectly.
What is going on, and how can I make my key assignment work?
As stated in the comments above, the command was assigned to another shortcut (something other than Cmd+R), and it worked. It was also suggested to restart the IDE.
Note: After the the command was reassigned, it was changed back to Cmd+R and it worked fine.
Super weird. After following Corné's suggestion I've assigned it to something else (cmd+option+shift+1). It worked. Then, I've changed it back to cmd+r and it suddenly started working with cmd+r too. It was probably a nasty Vscode bug.
I've created a basic node app following the steps described here - https://code.visualstudio.com/Docs/nodejs
Every time I run/debug (hit F5), VSCode automatically breaks at line 2 of this auto created debug file. The weird part is there is no breakpoint set.
I can continue past this and everything runs a-okay after, but it's super annoying to stop here every single time
Any ideas on getting rid of this? I've poured through the settings and nothing obvious stands out.
There is an option in the launch.json file called "stopOnEntry" (You can access the file by hitting the Configure icon on the Debug panel). Set it to false and it should solve your problem.
I am using Eclipse 3.4 and debugging Java. I have set a couple of breakpoints and that works fine. I run to a line and then it stops. I can inspect and all.
BUT If you I choose to enter a class or more I loose where the breakpoint actually was, that is where the debugger has stopped. I have to keep track of it myself and scroll back and stuff.
I just want to go back to where the last breakpoint was ( that is where the debugger has stopped )
How can I do that?
Thanks!
=== EDIT ===
I know that I can watch the call stack but nothing there is highlighted so it is a bit difficult.
I do not know of such a possibility.
However, depending on the number of active breakpoints you are using, maybe the "Breakpoints" view can help. Here you can see all breakpoints you have defined. If you make a doubleclick on an entry, Eclipse jumps to the corresponding source location.