Ultimate Automizer VS Code Extension
This extension runs a formal verification on the current active C file. It relies on Ultimate Automizer as external tool.
A formal verification by Ultimate Automizer on the file is performed and the results are embedded into the VS Code diagnostics.
Connection to a public server running Ultimate Automizer, e.g. https://monteverdi.informatik.uni-freiburg.de/ or https://ultimate.sopranium.de.
Alternatively a container providing the API can be executed inside Docker.
This extension contributes the following settings:
"stdout" to specify if Ultimate will be accessed by accessing a REST API or the output of the command line.
ultimate.url: Base URL of the REST API endpoint.
ultimate.executablePath: Path to the executable of Ultimate is NOT accessed by the REST API. This can either be Ultimate itself or the wrapper script for MacOS.
ultimate.settingsPath: Path to the settings (*.epf) of Ultimate is not accessed by the REST API.
ultimate.toolchainPath: Path to the toolchain (*.xml) of Ultimate is NOT accessed by the REST API.
ultimate.verifyOnSave: Enables verification on each file save (false by default)
- Make sure the right Java version us used as default version if running Ultimate locally.
- Windows version only working properly by using the REST API mode since Ultimate 0.2.3 was not working on my Windows test machine properly.
- The result representation (code highlighting, log output etc.) so far looks differently for
REST API and
stdout mode. This is due to the output of Ultimate in the two different modes.
- So far there is no Dockerfile/Image available to host the REST API backend locally in a container.
Add command to trigger verification manually (default now)
Add icon and compatibility for *.epf files.
The icon is used from the original Ultimate project here.