Install Prusti offline

Prusti Assistant

This Visual Studio Code extension provides interactive IDE features for verifying Rust programs with the Prusti verifier.

For advanced use cases, consider switching to the command-line version of Prusti.

Screenshot

An example of how verification errors are reported by the extension:

Requirements

In order to use this extension, please install the following components:

Java JDK version 11 or later, 64 bit. For example, OpenJDK.
Rustup version 1.23.0 or later. On Windows, this in turn requires the Microsoft C++ Build Tools.

If anything fails, check the "Troubleshooting" section below. Note that macOS running on M1 is currently not supported by this extension.

First Usage

Install the requirements (listed above) and restart the IDE.
- This will ensure that programs like rustup are in the program path used by the IDE.
Install the "Prusti Assistant" extension.
Open a Rust file to activate the extension.
- At its first activation, this extension will automatically download Prusti and install the required Rust toolchain.
Click on the "Prusti" button in the status bar.
- Alternativelly, you can run the Prusti: verify the current crate or file command.
- If the program is in a folder with a Cargo.toml file, Prusti will verify the crate in which the file is contained.
- If no Cargo.toml file can be found in a parent folder of the workspace, Prusti will verify the file as a standalone Rust program. No Cargo dependencies are allowed in this mode.
Follow the progress from the status bar.
- You should see a "Verifying crate [folder name]" or "Verifying file [name]" message while Prusti is running.
The result of the verification is reported in the status bar and in the "Problems" tab.
- You can open the "Problems" tab by clicking on Prusti's status bar.
- Be aware that the "Problems" tab is shared by all extensions. If you are not sure which extension generated which error, try disabling other extensions. (Related VS Code issue: #51103.)

To update Prusti, run the command Prusti: update verifier in the command palette.

If anything fails, check the "Troubleshooting" section below.

Features

Commands

This extension provides the following commands:

Prusti: verify the current crate or file to verify a Rust program. Clicking the "Prusti" button in the status bar runs this command.
Prusti: update verifier to update Prusti.
Prusti: show version to show the version of Prusti.
Prusti: restart Prusti server to restart the Prusti server used by the extension.
Prusti: clear diagnostics to clear all diagnostics generated by the extension.

Configuration

The main configuration options used by this extension are the following:

prusti-assistant.verifyOnSave: Specifies if programs should be verified on save.
prusti-assistant.verifyOnOpen: Specifies if programs should be verified when opened.
prusti-assistant.checkForUpdates: Specifies if Prusti should check for updates at startup.
prusti-assistant.javaHome: Specifies the path of the Java home folder. Leave empty to auto-detect it.
prusti-assistant.prustiVersion: Allows to choose between the latest published Prusti version (the default), a fixed release specified as a GitHub tag (see the list of releases), or a local build of Prusti.

Inline Code Diagnostics

This extension automatically provides inline diagnostics for Prusti errors.

Snippets

Basic code-completion snippets are provided for Prusti annotations.

Verification cache

By default, Prusti transparently caches verification requests. To clear the cache, it's enough to restart the Prusti server with the commands described above.

Prusti verification flags

The verification flags of Prusti can be configured in a Prusti.toml file. Its location should be the following:

When verifying a standalone Rust file, Prusti.toml should be placed in the same folder of the verified file.
When verifying a Rust crate, Prusti.toml should be placed in the innermost folder that (1) contains a Cargo.toml file and (2) transitively contains the current active file in the IDE.

In addition, due to a technical limitation the Prusti server reads its configuration flags from the Prusti.toml placed in the root of the IDE workspace (i.e. the navigation panel on the left). When modifying this file, it is necessary to manually restart the server. The server uses only a few of Prusti's flags, mainly to configure the verification cache and to decide whether to dump Viper files for debugging.

To check whether Prusti picked up the Prusti.toml that you wrote, try writing make_prusti_crash=true in it (or any other nonexistent configuration flag). When doing so, the IDE should report that Prusti crashed.

The list of the supported Prusti flags is available here, in Prusti's developer guide. Note that by setting these flags in the wrong way it is possible to get incorrect verification results. Many flags only exist of debugging reasons and to provide workarounds in selected cases.

Troubleshooting

If Prusti fails to run, you can inspect Prusti's log from VS Code (View -> Output -> Prusti Assistant) and see if one of the following solutions applies to you.

Problem	Solution
On Windows, Visual Studio is installed but the `rustup` installer still complains that the Microsoft C++ build tools are missing.	When asked which workloads to install in Visual Studio make sure "C++ build tools" is selected and that the Windows 10 SDK and the English language pack components are included. If the problem persists, check this Microsoft guide and this Rust guide. Then, restart the IDE.
The JVM is installed, but the extension cannot auto-detect it.	Open the settings of the IDE, search for "Prusti-assistant: Java Home" and manually set the path of the Java home folder. Alternatively, make sure that the `JAVA_HOME` environment variable is set in your OS. Then, restart the IDE.
Prusti crashes mentioning "Unexpected output of Z3" in the log.	Prusti is using an incompatible Z3 version. Make sure that the `Z3_EXE` environment variable is unset in your OS and in the settings of the extension. Then, restart the IDE.
`error[E0514]: found crate 'cfg_if' compiled by an incompatible version of rustc`	There is a conflict between Prusti and a previous Cargo compilation. Run `cargo clean` or manually delete the `target` folder. Then, rerun Prusti.
`error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the 'nightly-2021-09-20-x86_64-unknown-linux-gnu' toolchain` or `error[E0463]: can't find crate for std` or `error[E0463]: can't find crate for core`	The Rust toolchain installed by Rustup is probably corrupted (see issue rustup/#2417). Uninstall the nightly toolchain mentioned in the error (or all installed nightly toolchains). Then, rerun Prusti.
`error: no override and no default toolchain set`	Rustup has probably been installed without the `default` toolchain. Install it, then rerun Prusti.
`libssl.so.1.1: cannot open shared object file: No such file or directory` on Ubuntu 22.04	Ubuntu 22.04 deprecated `libssl1.1` and moved to `libssl3`. Consider this solution as a temporary workaround to install `libssl1.1`, or compile Prusti from source code to make it use `libssl3`.
On macOS running on an M1 chip, the extension doesn't work and the log contains messages such as `incompatible architecture (have (arm64), need (x86_64))`.	We currently don't release precompiled arm64 binaries for macOS. Until we do so, the only option is to compile Prusti from source code.

Thanks to @Pointerbender, @michaelpaper, @fcoury, @Gadiguibou, @djc for their help in reporting, debugging and solving many of these issues!

In case you still experience difficulties or encounter bugs while using Prusti Assistant, please open an issue or contact us in the Zulip chat.

	export function spawn(
	cmd: string,
	args?: string[] \| undefined,
	{ options, onStdout, onStderr }: {
	options?: childProcess.SpawnOptionsWithoutStdio;
	onStdout?: ((data: string) => void);
	onStderr?: ((data: string) => void);
	} = {},
	destructors?: Set<KillFunction>,
	): Promise<Output> {
	const description = `${cmd} ${args?.join(" ") ?? ""}`;
	log(`Run command '${description}'`);

	let stdout = "";
	let stderr = "";

	const start = process.hrtime();
	const proc = childProcess.spawn(cmd, args, options);
	const status: { killed: boolean } = { killed: false };
	log(`Spawned PID: ${proc.pid}`);

	// Register destructor
	function killProc() {
	if (!status.killed) {
	status.killed = true;
	// TODO: Try with SIGTERM before.
	treeKill(proc.pid, "SIGKILL", (err) => {
	if (err) {
	log(`Failed to kill process tree of ${proc.pid}: ${err}`);
	const succeeded = proc.kill("SIGKILL");
	if (!succeeded) {
	log(`Failed to kill process ${proc}.`);
	}
	} else {
	log(`Process ${proc.pid} has been killed successfully.`);
	}
	});
	} else {
	log(`Process ${proc.pid} has already been killed.`);
	}
	}
	if (destructors) {
	destructors.add(killProc);
	}

	proc.stdout.on("data", (data) => {
	stdout += data;
	try {
	onStdout?.(data);
	} catch (e) {
	log(`error in stdout handler for '${description}': ${e}`);
	}
	});
	proc.stderr.on("data", (data) => {
	stderr += data;
	try {
	onStderr?.(data);
	} catch (e) {
	log(`error in stderr handler for '${description}': ${e}`);
	}
	});

	function printOutput(duration: Duration, code: number \| null, signal: NodeJS.Signals \| null) {
	const durationSecMsg = (duration[0] + duration[1] / 1e9).toFixed(1);
	log(`Output from '${description}' (${durationSecMsg}s):`);
	log("┌──── Begin stdout ────┐");
	log(stdout);
	log("└──── End stdout ──────┘");
	log("┌──── Begin stderr ────┐");
	log(stderr);
	log("└──── End stderr ──────┘");
	log(`Exit code ${code}, signal ${signal}.`);
	}

	return new Promise((resolve, reject) => {
	proc.on("close", (code, signal) => {
	const duration = process.hrtime(start);
	printOutput(duration, code, signal);
	if (destructors) {
	destructors.delete(killProc);
	}
	resolve({ stdout, stderr, code, signal, duration });
	});
	proc.on("error", (err) => {
	const duration = process.hrtime(start);
	printOutput(duration, null, null);
	log(`Error: ${err}`);
	if (destructors) {
	destructors.delete(killProc);
	}
	reject(err);
	});
	});
	}

viperproject / prusti-assistant Goto Github PK

prusti-assistant's Introduction

Prusti Assistant

Screenshot

Requirements

First Usage

Features

Commands

Configuration

Inline Code Diagnostics

Snippets

Verification cache

Prusti verification flags

Troubleshooting

prusti-assistant's People

Contributors

Stargazers

Watchers

Forkers

prusti-assistant's Issues

Recommend Projects

Recommend Topics

Recommend Org