3
0
Fork 0
mirror of https://github.com/Z3Prover/z3 synced 2026-08-08 06:52:26 +00:00
No description
Find a file
Nikolaj Bjorner 07116de4b5 Harden cg-root generation tracking against interrupted merges (#10385)
Fixes state corruption that manifests as a SIGSEGV inside the MBQI model
checker's auxiliary context::check (regression after 4.16.0). The crash
sites vary per run (null enode in a worklist traversal, null enode in
boolean propagation, virtual dispatch through a freed justification) but
all share the pattern 'solver state corrupted, faults wherever it is next
touched'. The corruption originates in the new-in-5.0 machinery that
stores instantiation generations on congruence-class roots and replays
them across merges/unmerges.

Three unguarded spots in that machinery, each capable of producing that
pattern, are hardened:

1. get_cg_root() (smt_context.h): on a cg_table miss find() returns
   nullptr and callers immediately read ->m_generation, segfaulting
   (fault site 1). Fall back to treating n as its own root. Generations
   are a heuristic quantity, so this is sound and merely conservative
   while converting a crash into safe behaviour.

2. reinsert_parents_into_cg_table() (smt_context.cpp): the positional
   generation cache was consumed with unchecked indexing, unlike its
   sibling undo_add_eq() which already bounds-checks. A transiently
   desynced cache could read out of bounds and write a bogus generation.
   Bounds-check the index and fall back to get_generation(parent).

3. add_eq()'s catch(...) rollback (smt_context.cpp): remove_parents /
   reinsert_parents maintain two pieces of transient state not tracked by
   the trail stack -- marks on r1's parents and the m_r1_parent_generations
   scratch vector. If add_eq is interrupted between the two, a still-marked
   parent is silently skipped by the next remove_parents and a leftover
   cache entry desyncs the positional replay, arming the corruption for
   every later merge. Clear both before unwinding.

Also fixes an unrelated MSVC build break in seq_regex.cpp (a lambda
illegally captured the member reference 'ctx' by name instead of 'this').

Validated: seq_monadic unit tests pass; 90 MBQI runs over fstar-ulib
quantified VCs with an rlimit sweep (forcing cancellation mid-MBQI)
show no crashes or regressions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 57b9b87e-950a-49ea-bbb3-ed585646a5a9
2026-08-04 20:27:50 -07:00
.github Fix nightly release deployment tag permissions (#10383) 2026-08-04 12:32:12 -07:00
a3
cmake Fix uses of gnu anonymous structs. (#10345) 2026-08-01 11:44:01 -07:00
codeql/custom_queries
contrib
doc
docker
examples Remove tptp5 example 2026-07-29 14:01:08 -07:00
noarch
resources
scripts Load versioned libz3 soname in Python bindings on Linux (#10290) 2026-07-29 14:01:55 -07:00
src Harden cg-root generation tracking against interrupted merges (#10385) 2026-08-04 20:27:50 -07:00
.bazelrc
.clang-format
.dockerignore
.gitattributes
.gitignore
BUILD.bazel
build_z3.bat
CMakeLists.txt
configure
LICENSE.txt
MODULE.bazel
README-CMake.md
README.md Add F* master workflow badge to README build ribbons (#10279) 2026-07-28 11:53:53 -07:00
RELEASE_NOTES.md
Z3-AGENT.md
z3.log Fix releaseClang segfault: declare invoke_exit_action [[noreturn]], remove __builtin_unreachable() from UNREACHABLE() (#10295) 2026-07-29 13:23:43 -07:00
z3.pc.cmake.in
z3guide.jpeg

Z3

Z3 is a theorem prover from Microsoft Research. It is licensed under the MIT license. Windows binary distributions include C++ runtime redistributables

If you are not familiar with Z3, you can start here.

Pre-built binaries for stable and nightly releases are available here.

Z3 can be built using Visual Studio, a Makefile, using CMake, using vcpkg, or using Bazel. It provides bindings for several programming languages.

See the release notes for notes on various stable releases of Z3.

Try the online Z3 Guide

Build status

Pull Request & Push Workflows

WASM Build Windows Build CI OCaml Binding
WASM Build Windows CI OCaml Binding CI

Scheduled Workflows

Open Bugs Android Build Pyodide Wheel (PyPI) Nightly Build Cross Build F* Master Build
Open Issues Android Build Pyodide Wheel (PyPI) Nightly Build RISC V and PowerPC 64 F* Master Build
MSVC Static MSVC Clang-CL Build Z3 Cache Memory Safety Mark PRs Ready
MSVC Static Build MSVC Clang-CL Static Build Build and Cache Z3 Memory Safety Analysis Mark PRs Ready for Review

Manual & Release Workflows

Documentation Release Build WASM Release
Documentation Release Build WebAssembly Publish

Specialized Workflows

Nightly Validation Copilot Setup Agentics Maintenance
Nightly Build Validation Copilot Setup Steps Agentics Maintenance

Agentic Workflows

API Coherence Code Simplifier Release Notes Workflow Suggestion Academic Citation
API Coherence Checker Code Simplifier Release Notes Updater Workflow Suggestion Agent Academic Citation Tracker
Issue Backlog Memory Safety Report Specbot Crash Analyzer SMTLIB Benchmark Finder
Issue Backlog Processor Memory Safety Report Specbot Crash Analyzer SMTLIB Benchmark Finder
TPTP Benchmark
TPTP Front-End Benchmark

Building Z3 on Windows using Visual Studio Command Prompt

For 32-bit builds, start with:

python scripts/mk_make.py

or instead, for a 64-bit build:

python scripts/mk_make.py -x

then run:

cd build
nmake

Z3 uses C++20. The recommended version of Visual Studio is therefore VS2019 or later.

Security Features (MSVC): When building with Visual Studio/MSVC, a couple of security features are enabled by default for Z3:

  • Control Flow Guard (/guard:cf) - enabled by default to detect attempts to compromise your code by preventing calls to locations other than function entry points, making it more difficult for attackers to execute arbitrary code through control flow redirection
  • Address Space Layout Randomization (/DYNAMICBASE) - enabled by default for memory layout randomization, required by the /GUARD:CF linker option
  • These can be disabled using python scripts/mk_make.py --no-guardcf (Python build) or cmake -DZ3_ENABLE_CFG=OFF (CMake build) if needed

Building Z3 using make and GCC/Clang

Execute:

python scripts/mk_make.py
cd build
make
sudo make install

Note by default g++ is used as C++ compiler if it is available. If you prefer to use Clang, change the mk_make.py invocation to:

CXX=clang++ CC=clang python scripts/mk_make.py

Note that Clang < 3.7 does not support OpenMP.

You can also build Z3 for Windows using Cygwin and the Mingw-w64 cross-compiler. In that case, make sure to use Cygwin's own Python and not some Windows installation of Python.

For a 64-bit build (from Cygwin64), configure Z3's sources with

CXX=x86_64-w64-mingw32-g++ CC=x86_64-w64-mingw32-gcc AR=x86_64-w64-mingw32-ar python scripts/mk_make.py

A 32-bit build should work similarly (but is untested); the same is true for 32/64 bit builds from within Cygwin32.

By default, it will install z3 executables at PREFIX/bin, libraries at PREFIX/lib, and include files at PREFIX/include, where the PREFIX installation prefix is inferred by the mk_make.py script. It is usually /usr for most Linux distros, and /usr/local for FreeBSD and macOS. Use the --prefix= command-line option to change the install prefix. For example:

python scripts/mk_make.py --prefix=/home/leo
cd build
make
make install

To uninstall Z3, use

sudo make uninstall

To clean Z3, you can delete the build directory and run the mk_make.py script again.

Building Z3 using CMake

Z3 has a build system using CMake. Read the README-CMake.md file for details. It is recommended for most build tasks, except for building OCaml bindings.

Building Z3 using vcpkg

vcpkg is a full platform package manager. To install Z3 with vcpkg, execute:

git clone https://github.com/microsoft/vcpkg.git
./bootstrap-vcpkg.bat # For powershell
./bootstrap-vcpkg.sh # For bash
./vcpkg install z3

Building Z3 using Bazel

Z3 can be built using Bazel. This is known to work on Ubuntu with Clang (but may work elsewhere with other compilers):

bazel build //...

Dependencies

Z3 itself has only few dependencies. It uses C++ runtime libraries, including pthreads for multi-threading. It is optionally possible to use GMP for multi-precision integers, but Z3 contains its own self-contained multi-precision functionality. Python is required to build Z3. Building Java, .NET, OCaml and Julia APIs requires installing relevant toolchains.

Z3 bindings

Z3 has bindings for various programming languages.

.NET

You can install a NuGet package for the latest release Z3 from nuget.org.

Use the --dotnet command line flag with mk_make.py to enable building these.

See examples/dotnet for examples.

C

These are always enabled.

See examples/c for examples.

C++

These are always enabled.

See examples/c++ for examples.

Java

Use the --java command line flag with mk_make.py to enable building these.

For IDE setup instructions (Eclipse, IntelliJ IDEA, Visual Studio Code) and troubleshooting, see the Java IDE Setup Guide.

See examples/java for examples.

Go

Use the --go command line flag with mk_make.py to enable building these. Note that Go bindings use CGO and require a Go toolchain (Go 1.20 or later) to build.

With CMake, use the -DZ3_BUILD_GO_BINDINGS=ON option.

See examples/go for examples and src/api/go/README.md for complete API documentation.

OCaml

Use the --ml command line flag with mk_make.py to enable building these.

See examples/ml for examples.

Python

You can install the Python wrapper for Z3 for the latest release from pypi using the command:

   pip install z3-solver

Use the --python command line flag with mk_make.py to enable building these.

Note that it is required on certain platforms that the Python package directory (site-packages on most distributions and dist-packages on Debian-based distributions) live under the install prefix. If you use a non-standard prefix you can use the --pypkgdir option to change the Python package directory used for installation. For example:

python scripts/mk_make.py --prefix=/home/leo --python --pypkgdir=/home/leo/lib/python-2.7/site-packages

If you do need to install to a non-standard prefix, a better approach is to use a Python virtual environment and install Z3 there. Python packages also work for Python3. Under Windows, recall to build inside the Visual C++ native command build environment. Note that the build/python/z3 directory should be accessible from where Python is used with Z3 and it requires libz3.dll to be in the path.

virtualenv venv
source venv/bin/activate
python scripts/mk_make.py --python
cd build
make
make install
# You will find Z3 and the Python bindings installed in the virtual environment
venv/bin/z3 -h
...
python -c 'import z3; print(z3.get_version_string())'
...

See examples/python for examples.

Julia

The Julia package Z3.jl wraps the C API of Z3. A previous version of it wrapped the C++ API: Information about updating and building the Julia bindings can be found in src/api/julia.

WebAssembly / TypeScript / JavaScript

A WebAssembly build with associated TypeScript typings is published on npm as z3-solver. Information about building these bindings can be found in src/api/js.

Smalltalk (Pharo / Smalltalk/X)

Project MachineArithmetic provides a Smalltalk interface to Z3's C API. For more information, see MachineArithmetic/README.md.

AIX

Build settings for AIX are described here.

System Overview

System Diagram

Interfaces

Power Tools