In the Preference dialog the selection for Java->Compiler->Error/Warnings, changing the option for "Empty Statement" in the Potential Programming Problems section to any value other than Error seems to be ignored. I have tried changing the option at both global and project levels with the same result. Regardless of the option value anytime a line is ended with a double semicolon it is reported as a Syntax Error.
Is this a known problem and is there a solution or work-around. I am running into this problem in code that I have no authorization to change.
Related
When I try to run a Node.js debugging session from Visual Code, the debugging console returns an error, saying that the bootloader.bundle.js could not be found. However, the bootloader.bundle.js file exists at the expected location, while the debug console specifies the folder incorrectly by substituting a UTF-8 character (letter č) with the replacement character (�). The snippet of the error message can be found below:
Error: Cannot find module 'c:/Users/xxxx xxxx�/AppData/Local/Programs/
Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js'
Can I somehow fix this in VS Code, perhaps by modifying the launch.json file in some way or some other settings?
Any help is appreciated!
EDIT:
I temporarily fixed the issue by reinstalling VS Code to another folder without that doesn't include diacritical characters. I'd like to to keep this question open, however, in case somebody knows of a way to fix this sort of problem (e.g. by by modifying some configuration files) that does not require either reinstalling or relying on a portable version of the app.
I have just dealt with the same issue. There have been Unicode characters in my folder's path and I got the same error "Cannot find module". Reasons are described in details here.
To fix it I have gone to File - Preferences - Settings and then entered "usePreview" and then I unchecked the option "Use the new in-preview JavaScript debugger for ..." under the section "Debug > JavaScript: Use Preview" and reloaded VS Code. The issue has gone.
I swear I used to remember Visual Studio just breaking on an exception. It would take you straight to the line where the exception was thrown and allowed you to inspect variables just by hovering over them.
Or maybe that was a dream. Or maybe this is a nightmare.
But it's actually not a problem, right, because now instead of it just working all you need to do is go to Debug > Windows > Exception Settings where you get this mess.
Which has many glaring problems. For example:
Remember when I said it used to just work?
I don't have all these Exception types memorized.
Clicking toggle all on/off removes your previous selections.
Oh and also, clicking this checkbox does absolutely nothing
It used to just work. Is it possible to get it back to just doing that?
Under exception settings, Go to Common Language Runtime Exceptions->check all. This will not break your application, but show you the exact line of occurrence of the exception.
Per that first image you posted, it appears the application is throwing an exception in "external" code, so you likely have the "Just My Code" enabled in the debugging options. Try unchecking that "Just My Code" option via your Tools|Options dialog (Debugging\General category), and that'll likely fix you up.
FYI, I am using a MCVS 2013 to build and run my program. However, I kept getting the error as shown in the picture, I have try to google the solution out, but there are no much information available. Besides that, I also getting 127 warnings. Some one from here please tell me how to prevent this error happen. Thanks!
In the properties page for your project, under the Linker -> Debugging tab, you need to use true or false instead of Debug as shown in the figure I attached.
I am building an automation suite using Xcode 7 with swift.
My app loads with the following Alert View:
Allow "Light Alarm" to access your location while you use the app?
When I record with UI Testing and click this alert I get the following code:
app.alerts["Allow \U201cLight Alarm\U201c to access your location while you use the app?"]
Note: The quotes has been replaced with \U201c
However, when I try and compile I get the following error:
"Invalid escape sequence in literal"
Anyone know how to get round this?
This seems to be a bug in Xcode when generating code during UI recording.
Swift uses \u{NNNN} escape sequences in string literals, so
app.alerts["Allow \u{201c}Light Alarm\u{201c} ..."]
would be correct, or simply
app.alerts["Allow “Light Alarm“ ..."]
(Actually it should be "Allow “Light Alarm” ..." where the
second quotation mark is U+201D = RIGHT DOUBLE QUOTATION MARK :)
A similar issue for UI recorded code in Objective-C was reported in
Incomplete universal character name in UI Testing.
I do not know a workaround, it seems that the only thing you can do
at present is to fix the code after recording (and sent a bug report
to Apple).
Installing Xcode 7.3 fixed this issue for me
Environment: Xcode Version 5.0.1 (5A2034a)
Scenario:
1) I've create a simple Apple-supplied iOS project template.
2) I create a local string value with an initial value; plus a local integer variable with value.
3) I did a debug 'po' & 'p' for the object and integer.
Xcode's debugger apparently doesn't see these values.
The following are a couple of snippets of the debugger's environment:
As you can see, the debugger's symbol-generator is ON and the optimization is set to NO (zero).
1) Here's another example.
Note: NSLog() does work.
Notice the 'Turkey' for 'testString' value. Why this value?
'Turkey' was used in ANOTHER project and has no relevance to this one sample project.
It appears that I'm getting variable bleed from some xcode environment peculiar to Xcode 5;
...not found/experienced in Xcode 4.
Okay, this is weird. I've tried the NSLog() and got the values displayed. Then just for kicks I did a 'po' again and got the correct value.
However I still have the 'Turkey' value:
2) Here's a second example.
Starting with a new application from the Apple-supplied view template:
This time, the NSLog() works but again, can't get the 'po' value.
I still haven't figured out the pattern here.
What else can I do?
How can I get my debugger 'po' & 'p' commands to show data?
Or... why am I'm getting inconsistent debugger behavior (Xcode5 appears to work okay; re 'NSLog()')?
I had this recurrent problem so I tried logging via a different account to find the problem disappeared.
So there's something wrong with my Xcode account; specifically:
So I emptied the Xcode folder found under ~/Library/Developer and restarted Xcode.
Apparently the problem(s) is/are solved.