VScode C debug problem with unable to find corresponding c file - visual-studio-code

When I use vscode debug, and upon meeting function like printf(), it will generate an error message saying the certain file cannot be found
Unable to open 'acrt_iob_func.c': Unable to read file
'c:_\M\mingw-w64-crt-git\src\mingw-w64\mingw-w64-crt\stdio\acrt_iob_func.c'
(Error: Unable to resolve non-existing file
'c:_\M\mingw-w64-crt-git\src\mingw-w64\mingw-w64-crt\stdio\acrt_iob_func.c').
The C file at the end (acrt_iob_func.c) varies.
Using gcc as my compiler help are appreciated.

Skip command to add into launch.json under "setupCommands" for muting warning:
{
"description": "Skip stdio-common files",
"text": "-interpreter-exec console \"skip -gfi stdio/*.c\""
},

Related

Databricks Extension Fails for Visual Studio Code

I try to install extension below on VS Code, but nothing happens when I click "Configure Databricks"
Extension:
https://marketplace.visualstudio.com/items?itemName=databricks.databricks&ssr=false#qna
Details from Developer: Toggle Developer Tools
ERR Command failed:
c:\Users\user.name.vscode\extensions\databricks.databricks-0.2.3-win32-x64\bin\bricks
auth profiles --skip-validate Error: cannot parse config file: open
C:\Test" /M: The filename, directory name, or volume label syntax is
incorrect. : Error: Command failed:
c:\Users\user.name.vscode\extensions\databricks.databricks-0.2.3-win32-x64\bin\bricks
auth profiles --skip-validate Error: cannot parse config file: open
C:\Test" /M: The filename, directory name, or volume label syntax is
incorrect.
at ChildProcess.exithandler (node:child_process:408:12) at
ChildProcess.emit (node:events:526:28) at maybeClose
(node:internal/child_process:1092:16) at Socket.
(node:internal/child_process:451:11) at Socket.emit
(node:events:526:28) at Pipe. (node:net:687:12)
How can I fix it? Does anyone else had any issues?
It seems like the extension can't read your Databricks profile (~/.databrickscfg). Check if the file exists and if it contains potentially problematic contents.
I've create a ticket to track this issue https://github.com/databricks/databricks-vscode/issues/462

Vs Code : Error: could not open `C:\Users\folder-name'

I was trying to implement a Spring boot application on vs code and came up with this error when I tried to run the code (Screenshot below). I am not clear what this error indicates and did not know what exactly to look for on the internet. could anyone tell me how I can resolve this error?
edit:
as I was told to copy-paste the error message as text, here it is.
PS D:\study material\java code\springbootdemo> cd 'd:\study material\java code\springbootdemo'; & 'c:\Users\manjeet arneja\.vscode\extensions\vscjava.vscode-java-debug-0.27.0\scripts\launcher.bat' 'C:\Program Files\AdoptOpenJDK\jdk-11.0.6.10-hotspot\bin\java.exe' '-Dfile.encoding=UTF-8' '#C:\Users\manjeet' 'arneja\AppData\Local\Temp\cp_9w87n9v9bnokxm9i3k10qtvnm.argfile' 'com.explore.springbootdemo.DemoApplication'
Error: could not open `C:\Users\manjeet'

Sikuli IDE Error - javax.script.ScriptException " is not defined in nashorn:mozilla_compat.js at line number 69

I'm working on a simple Sikuli Script.
The script is simply one line shown below
click()
The following error is produced?
javax.script.ScriptException: ReferenceError: "Commands" is not defined in nashorn:mozilla_compat.js at line number 69
I believe I have all dependencies installed. Could I ask for some assistance for what else is missing to move on from this error?
You are trying to use the commands in javascript mode. Do the following: create a new tab, right click on it, select "set type" and choose "jython". Your code should now work.

info: Trying to load file 'OEMFMFileList.xml' as a FM file list ... fatal error : Error: Missing package - Creating basic IoT Core Image Powershell

I am just trying to create a basic IoT core image by following this guide.
But I am always getting the below errors, whenever I run buildimage <product name> Test after building the BSP (Import-IoTBSP RPi2 C:\Downloads\RPi_BSP.zip (or) importbsp RPi2 C:\Downloads\RPi_BSP.zip
buildpkg RPi2)
info: Trying to load file 'C:\OEEWorkspace\Build\arm\InputFMs\OEMFMFileList.xml' as a FM file list ... fatal error : Error: Missing package: C:\OEEWorkspace\Build\arm\pkgs\test.OEM.Sample.cab
info: Trying to load file 'C:\OEEWorkspace\Build\arm\InputFMs\RPi2FMFileList.xml' as a FM file list ... fatal error : Error: Missing package:
I also followed this issue in GitHub, but couldn't find the exact issue. Have you ever faced any error something similar?
Huh!. It was a silly mistake. I didn't run the New-IoTCabPackage All (or) buildpkg all after building the BSP (Import-IoTBSP RPi2 C:\Downloads\RPi_BSP.zip (or) importbsp RPi2 C:\Downloads\RPi_BSP.zip
buildpkg RPi2). Hence the cab files were not pushed into the Build\arm\pkgs folder.
After running the buildpkg all I am able to see all the required cab files in the pkgs folder, thus no error. You must do the commands in the below order.
PS C:\OEE>importbsp RPi2 "C:\Users\SibeeshVenu\Downloads\RPi_BSP.zip"
PS C:\OEE>buildpkg all
PS C:\OEE>newproduct OEEIoTCore RPi2
PS C:\OEE>buildimage OEEIoTCore Test
Once that is done, you should be able to see an output as below.

wurfl2 integration in TYPO3

everytime i try to install the wurfl2 extension in TYPO3 i get the following error message:
Fatal error: require_once() [function.require]: Failed opening required '' (include_path='.:/usr/local/php/lib/php:/usr/local/php/lib/php/PEAR') in /html/typo3conf/temp_CACHED_ps9b8e_ext_localconf.php on line 501
is anyone familiar with this error and knows how to fix it?
I get the same error message with TYPO3 4.4.4. I had to remove the extension folder and to delete all ./typo3conf/temp* files to get Typo3 running again afterwards.
(You might not see the error message if you don't have something like $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1' in your localconf.php. You can set this with the installtool.
As already mentioned by the other answer first you have to get your system running again: set $TYPO3_CONF_VARS['SYS']['displayErrors'] = '1' in your localconf.php in order to see all error messages. Afterwards remove the extension folder.
I think the error is caused by a missing config file. The extension constant wurflConfig has to be set with the absolute path to the file /YOUR/PATH/TO/WEB_DIR/typo3conf/ext/wurfl2/res1/li/wurfl_config.php and might have to adjust the settings there.