I start the debugger with "slc debug" and Chrome starts up. I want to set a breakpoint on line 100 of report.js
I can't do it. Won't let me.
Any ideas why?
In other file such as events.js I can click on the linenumber and the blue breakpoint shows up.
Is the Strongloop node inspector any different from the standard one?
I got this problem too. Try this (sound weird), but its work for me :
type "slc debug"
the chrome will open up, with one new tab
explore to your "report.js" file, set break point at your line (Note : the break point will not show)
open up new tab at same chrome
type in the debug path (same like the one at step 2, or you can see it at your debugger). ex : http://localhost:8080/debug?port=5858
At the new debug tab, the break point will show up.
Hope it help, just sharing what i been through.
thanks.
Related
I am using latest iTerm on catalina with the "Semantic History" feature which allows you to Cmd+Click urls and filename/paths in the terminal. I set iTerm to open vscode:
This seems to work well if the text is like "src/foo/bar.js:3:3" - however if the text is like "src/foo/bar.js" it treats it like a file url. When you hold CMD and hover over these pure file paths, it shows the full file url in the bottom right, just like when you hover over links inside a browser:
What ends up happening with the file:// url is it will open the default app specified by the OS. On one hand, iterm should be smart enough to know that we want to open files in our editor... On the other hand, it would be nice if Jest also added the column and line number for iterm to recognize.
Turns out, clicking the last stack frame at bottom of the stack trace goes directly to the highlighted error line+column number.
I just npm init in an empty folder that didn't do anything, but Debug is floating as shown in the picture.
Why is this floating?
Does this interfere with the error?
If it interferes, is there any way to get rid of it?
I would really appreciate it if you let me know.
This is not an error and the "debug" text is not actually part of the file.
VSCode inserts the "debug" button as a shortcut for running the scripts in the package.json file. When you click on it, a popup will appear allowing you to select the script you want to run or debug.
I thought the reason the new VS Code debugger stopped on the 'use strict'; in my file was because of some weird deprecatory behaviour in new versions of Node, or else because my code had some weird error in it.
Then I realised that "break on first line" is a thing, and one that people want. Why on earth is this a thing? I know that my script has a first line, thank you very much. I'd have bigger problems if it didn't. So why does the debugger need to do this?
In launch.json there is a property stopOnEntry which is set to true by default. If you don't want to Node Debugger to "break on first line" set this property to false.
Now a toggle for this exists:
--inspect vs --inspect-brk
The reason "break on first line" is a feature, is so that you can run your application, and have it stop on the first line before continuing.
This allows you to attach a debugger before Node has executed some of the code. This enables you to debug the very first lines of code, set more breakpoints, or step over the lines of code whenever you are ready.
This is actually a pretty common feature in a debugger, especially if you don't necessarily have a way to set breakpoints before you run the code.
When I test my web page.
This error message I got.After this messge, I am not able to proceed with my web page.
Can you explain me how to rectify from this?
This is because u have kept the break point in your source scripts.If you want to ignore this just close the Console window or simply press f8
Getting this error while trying to compile and run app.
Since the only work I have done is on the XIB file, I have tried removing the value from the launch screen file box, still it didn't help.
Here's a screenshot:
http://i.imgur.com/mCtsdUr.png
Using Xcode 6.1.
If you set outlet connection with any of the object of launch screen then it's give this types of error.Simply launch screen has a plain(static) UI. You can not change it's value run time or using creating UIViewcontroller. So, remove all outlet connection of launch screen. If you want remove Launch Screen then go to General setting tab then clear value of Launch Screen file. Make sure it's also clear into the info.plist file.