AI Augmented ESBMC processing. Passes the output from ESBMC to an AI model that allows the user to use natural language to understand the output. As the output from ESBMC can be quite technical in nature. The AI can also be asked other questions, such as suggestions on how to fix the problem outputted by ESBMC, and to offer further explanations.
This is an area of active research.
demo.webm
demo_fix_code.webm
More videos can be found on the ESBMC-AI Youtube Channel
From the ESBMC website:
ESBMC is an open source, permissively licensed, context-bounded model checker based on satisfiability modulo theories for the verification of single and multi-threaded C/C++ programs. It does not require the user to annotate the programs with pre- or postconditions, but allows the user to state additional properties using assert-statements, that are then checked as well. Furthermore, ESBMC provides two approaches (lazy and schedule recording) to model check multi-threaded programs. It converts the verification conditions using different background theories and passes them directly to an SMT solver.
From the ESBMC GitHub repo
The efficient SMT-based context-bounded model checker (ESBMC)
- Install required Python modules:
pip3 install -dr requirements.txt
. Alternatively usepipenv shell
to go into a virtual environment and runpipenv lock -d
to install dependencies from the Pipfile. - ESBMC-AI does not come with the original ESBMC software. In order to use ESBMC-AI you must provide ESBMC. Download ESBMC executable or build from source.
- Once the ESBMC software is downloaded, open
config.json
and edit theesbmc_path
field to specify its location, it's recommended for development purposes to either install it globally or have it in the project root. - Create a
.env
file using the provided.env.example
as a template (use commandcp .env.example .env
). Make sure to insert your OpenAI API key inside the.env
file you just created! - Further, adjust
.env
settings as required. - Further, adjust the
config.json
file as required. Be careful when editing AI model messages as incorrect messages can break the flow of the program, or introduce incorrect results. In general, it's recommended to leave those options alone. - You can now run ESBMC-AI.
The following settings are adjustable in the .env file. Some settings are allowed to be omitted, however, the program will display a warning when done so as it is not a recommended practice. This list may be incomplete:
OPENAI_API_KEY
: Your OpenAI API key.ESBMC_AI_CFG_PATH
: ESBMC AI requires a path to a JSON config file, the default path is./config.json
. This can be changed to another path, if there is a preference for multiple files.
The following settings are adjustable in the config.json
file. Some settings are allowed to be omitted, however, the program will display a warning when done so as it is not a recommended practice. This list may be incomplete:
chat_temperature
: The temperature parameter used when calling the chat completion API. This controls the temperature sampling that the model uses. Higher values like 0.8 and above will make the output more random, on the other hand, lower values like 0.2 will be more deterministic. Allowed values are between 0.0 to 2.0. Default is 1.0ai_model
: The model to use. Options:gpt-3.5-turbo
,gpt-4
(under API key conditions).esbmc_path
: Override the default ESBMC path. Leave blank to use the default ("./esbmc").cfg_sys_path
: Path to JSON file that contains initial prompt messages for the AI model that give it instructions on how to function.cfg_initial_prompt_path
: Text file that contains the instructions to initiate the initial prompt, where the AI is asked to walk through the code and explain the ESBMC output.esbmc_params
: Array of strings. This represents the default ESBMC parameters to use when calling ESBMC, these will be used only when no parameters are specified after the filename. Do not specify a source file to scan in here as ESBMC-AI will inject that in the ESBMC parameters itself.prompts
: Contains the prompts that will be used when setting up/interacting with the AI.system
: Array of initial system messages that instruct the AI what its function is. Each element in the array is a struct that contains arole
field (should ideally be system/assistant) and acontent
field that describes what that role's message content are. This should be a conversation between system and assistant.initial
: String that describes the initial prompt given to the AI, after it has read the source code, and the ESBMC output. This field should ask the AI model to explain the source code and ESBMC output.
ESBMC-AI can be used to scan a file with default parameters like this:
./esbmc_ai.py /path/to/source_code.c
Any parameters before the filename will be processed and consumed by ESBMC-AI.
So in this case -vr
will be consumed by ESBMC-AI, and ESBMC will not get any
arguments.
./esbmc_ai.py -vr /path/to/source_code.c
./esbmc_ai.py -h
Below are some very useful arguments that can be passed to ESBMC:
Property checking:
--compact-trace add trace information to output
--no-assertions ignore assertions
--no-bounds-check do not do array bounds check
--no-div-by-zero-check do not do division by zero check
--no-pointer-check do not do pointer check
--no-align-check do not check pointer alignment
--no-pointer-relation-check do not check pointer relations
--no-unlimited-scanf-check do not do overflow check for scanf/fscanf
with unlimited character width.
--nan-check check floating-point for NaN
--memory-leak-check enable memory leak check
--overflow-check enable arithmetic over- and underflow check
--ub-shift-check enable undefined behaviour check on shift
operations
--struct-fields-check enable over-sized read checks for struct
fields
--deadlock-check enable global and local deadlock check with
mutex
--data-races-check enable data races check
--lock-order-check enable for lock acquisition ordering check
--atomicity-check enable atomicity check at visible
assignments
--stack-limit bits (=-1) check if stack limit is respected
--error-label label check if label is unreachable
--force-malloc-success do not check for malloc/new failure
Some examples of passing parameters to ESBMC:
./esbmc_ai.py /path/to/source_code.c --force-malloc-success --no-assertions --unwind 5
Basically, any arguments after the filename are passed directly to ESBMC.
Type the following command when inside the chat:
/help
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.