Skip to content

Cart

Your cart is empty

Installing and Using AbsInt Astrée with Visual Studio Code
AbsInt

Installing and Using AbsInt Astrée with Visual Studio Code

AbsInt Astrée can be integrated with Visual Studio Code using the A3C extension, allowing developers to run Astrée analysis and review detected alarms directly within the editor.


Install and Configure A3C


  1. Open Visual Studio Code and press Ctrl + Shift + X.
  2. Search for the A3C / Astrée extension and install it.
  3. Configure the Astrée installation path if prompted.
  4. Open your C/C++ project folder in VS Code.

 

Once configured, A3C connects VS Code with Astrée and can automatically start an analysis when a source file is opened.

 

Running the Analysis

For Single Translation Unit analysis, go to:

Manage → Settings → Workspace → Extensions → A3C for C/C++ LSP Client

 

Change the view from Full Project to Single Translation Unit.

 

Now, when you open a source file, Astrée automatically starts the analysis. Opening another source file triggers a new analysis for that file.

 

Detected alarms appear directly in the editor as red squiggly indicators, with additional information available in the Problems and Output panels.

 

A single-click analyzes a file temporarily, while a double-click keeps the results available, allowing alarms from multiple files to be reviewed together.

 

You may also see a .dax file at the top level of an Astrée project:

Project/
├── project.dax
└── src/
    ├── main.c
    ├── module1.c
    └── module2.c

 

The .dax file is not source code. It contains the Astrée project/analysis configuration and defines how Astrée should analyze the source code. This is why it is typically kept at the project level rather than inside the source directory.

 

See It in Action

 

The complete workflow is also demonstrated at approximately the 26-minute mark of our webinar:

Integrating AbsInt Static Analysis Tool with the KEIL Studio and using VS code


RELATED NEWS

Modern Embedded Debugging with Keil Studio for Visual Studio Code
Hrutik Champaneri

Modern Embedded Debugging with Keil Studio for Visual Studio Code

Visual Studio Code has rapidly become a preferred development environment for embedded software, and many engineering teams are now looking beyond editing and building firmware. The Arm Keil Stud[...]

Read more
Running Arm User-Based Licensing in Modern CI/CD Workflows
Hrutik Champaneri

Running Arm User-Based Licensing in Modern CI/CD Workflows

Modern embedded software development no longer ends at a successful local build. Firmware is now continuously compiled, tested, analyzed, and packaged through automated pipelines running on Jenki[...]

Read more
Virtual Platforms as a Foundation for Modern Embedded Development
Hrutik Champaneri

Virtual Platforms as a Foundation for Modern Embedded Development

Modern embedded software development is no longer limited to writing code and waiting for a physical target. As engineering teams adopt CI/CD pipelines, distributed development, and parallel hard[...]

Read more
QA-MISRA 26.04: Faster Analysis, Smarter Reporting, Greater Flexibility
Karen O'Connell

QA-MISRA 26.04: Faster Analysis, Smarter Reporting, Greater Flexibility

The new release delivers significant improvements in performance, reporting accuracy, and workflow flexibility for teams developing safety- and business-critical software. It introduces ...

Read more
Cantata 26.04: Bringing AI-Assisted Testing into the Verification Workflow
Karen O'Connell

Cantata 26.04: Bringing AI-Assisted Testing into the Verification Workflow

The new release introduces new AI-assisted testing capabilities, enhanced automation, and greater flexibility for teams developing safety-critical C and C++ software. Highlights include...

Read more