Troubleshooting for VSCode configuration
If you have the error message in the following image. Please make sure your VSCode is working under the correct folder. Click “File” -> “Folder” then switch to "/home/SVF-tools/SVF-Teaching/ “ as your current working directory.
If you are using M1 chip Mac, you may not be able to debug using the default docker image. Building from scratch is useful for those on systems not fully supported right now (M1 Mac is probably the most common) or those who want to use their own tooling rather than VSCode.
You can also set up Teaching-Software-Analysis using Google Computing Platform.
- Download MacOSX11.3.sdk and put it under the directory
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ - Create a soft link:
sudo ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk
If everything else is working otherwise, you can ignore this. During source-level debugging, VSCode is looking for some source for some library code that is executed along with your program but while the compiled library is available, the source is not.
We should be able to trust these system libraries and so we don't need to debug them for the rest of the world. :)
- In the settings, set the C_Cpp Intelli Sense Engine field to Default (search for C_Cpp.intelliSenseEngine).
- In the file .vscode/c_cpp_properties.json, change line 13 to "compilerPath": "/usr/bin/g++", line 16 to "intelliSenseMode": "linux-gcc-x64"
If you have any compilation errors when setting up your IDE, resolve it by reloading the latest docker image in your VSCode following this page