Skip to content

This extension runs a formal verification on the current active C file. It relies on Ultimate Automizer as external tool.

License

Notifications You must be signed in to change notification settings

FahrJo/ultimate-automizer-vscode

Repository files navigation

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.

Features

A formal verification by Ultimate Automizer on the file is performed and the results are embedded into the VS Code diagnostics.

demonstration

Requirements

Connection to a public server running Ultimate Automizer, e.g. https://ultimate.sopranium.de/api.

Alternatively a container providing the API can be executed inside Docker. A dockerfile to host the Backend locally can be found here.

Extension Settings

This extension contributes the following settings:

  • ultimate.mode: "rest-api"/"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.refreshDelay: Refresh rate for polling results from REST API (limited to 3 seconds for known public APIs).
  • 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. A default toolchain is used if not defined.
  • ultimate.verifyOnSave: Enables verification on each file save (false by default)

Known Issues

  • Make sure the right Java version is used as default version if running Ultimate locally.
  • Windows version only working tested 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.

Release Notes

0.3.0

Change default public REST-API endpoint. The old one was broken.

0.2.3

Add ability to stop ongoing verification, bugfixes and dependency updates

0.2.2

Add support for highlighting assertions where context from Ultimate is missing

0.2.0

Change to new REST-API of Ultimate

0.1.2

Add command to trigger verification manually (default now)

0.1.1

Add icon and compatibility for *.epf files.

0.1.0

Initial release

Acknowledgements

The icon is used from the original Ultimate project here.

About

This extension runs a formal verification on the current active C file. It relies on Ultimate Automizer as external tool.

Topics

Resources

License

Stars

Watchers

Forks

Contributors 3

  •  
  •  
  •