1.5.14. Migration to 7.11.0¶
Caution
Starting with this release, the Axivion Suite now comes with its own Python interpreter
that is used by default if no other interpreter is set with BAUHAUS_PYTHON.
To restore the old behavior and search for a Python interpreter only on the system, set
BAUHAUS_PYTHON=auto. For alternatives, see BAUHAUS_PYTHON.
1.5.14.1. AxivionC#Frontend¶
To simplify configuration, the option to create an RFG was removed from AxivionC#Frontend, and some configuration parts now require manual adjustment.
Required actions:
If a filename with the extension
.rfgis configured in the fieldoutput, the analysis will abort with an error. Use the extension.cspkginstead.Previously, AxivionC#Frontend required the /Project/rfg option to be set to the name of the generated RFG file. This is no longer necessary; setting this option will now produce an error if AxivionC#Frontend is used.
To specify a custom RFG output filename, use the same configuration options as those for C/C++ analyses. See the rule SaveRFG for more information.
1.5.14.2. Dashboard¶
General Settings¶
The General Settings page has been migrated to the new look and feel and divided into subsections. The page can be accessed with administrator privileges via the settings menu button in the top-right section of the header, just as with the old interface.
Additionally, applying settings now requires explicit saving (if applicable) using the new Save button at the bottom of the settings pages.
Supplementary information, if available, can be toggled via the info button located to the right of the section header.
Legacy Mailer¶
The per-project setting Prefer Legacy Mailer has been removed.
Starting with version 7.5.0, the analysis component no longer checks this setting and
is therefore unable to use the CI-configured mailer.
If an analysis project using Axivion Suite version < 7.5.0 needs to communicate with a
Dashboard version >= 7.11.0 and is configured to use
the CI-based mailer, you must either switch to the
Dashboard integrated mailer
or use our API to send notification emails (see, e.g.,
example/reports/report_delta_mailer.py).
In the former case, we recommend performing the migration before updating the Dashboard
and consulting the documentation for version < 7.11.0, as it contains hints
on how to perform this migration.
Reports¶
The example report modules located in the example/reports directory have
been updated to remove the outfile option. Reports are now automatically
named based on the project for which they are generated.
Note
The example modules—both visualization and report modules—in
example/reports are not part of the stable API and may be subject to
changes without explicit notice. Therefore, it is recommended to copy them outside
the Axivion Suite installation directory before customizing or using them.
Starting with 7.11.0, the dashserver start and dashserver
install commands will automatically copy all modules from
example/reports to <confdir>/modules, where <confdir>
is the Axivion Dashboard Server configuration directory.
If the Axivion Dashboard Server is configured to search for report modules inside the
Axivion Suite installation directory and relies on the outfile option, ensure a backup of the old modules is created prior to the upgrade. Moreover, if you
have automated tasks that create reports via report_runner, ensure the
outfile option is removed from those tasks.
1.5.14.3. Java¶
JDK builds from jdk.java.net are no longer officially supported for running the Dashboard or viewing Local Build or Single File Analysis results. While they should continue to function, please refer to our Dashboard Installation Guide for explicitly recommended JVMs.
1.5.14.4. Axivion Suite Plugin for Visual Studio Code¶
The Single-File Analysis settings for the Axivion Suite Plugin for Visual Studio Code now expect an array of Single-File Analysis configurations instead of a single configuration; for example:
"axivion.singleFileAnalysis": [
{
"command": "${workspaceFolder}\\Axivion\\single_file_analysis_scenario_1.bat ${file}"
"bauhausConfig": "${workspaceFolder}\\Axivion",
},
{
"command": "${workspaceFolder}\\Axivion\\single_file_analysis_scenario_2.bat ${file}"
"bauhausConfig": "${workspaceFolder}\\Axivion",
}
]
If the array contains multiple entries, you will be prompted to select a configuration when running a Single-File Analysis in Visual Studio Code.
This change will not break existing Single-File Analysis configurations, but it will trigger linter warnings in the configuration file.
1.5.14.5. Axivion Suite Plugin for Visual Studio¶
The plugin now supports Visual Studio 2026 (aka Visual Studio 18 Insiders).
The minimum .NET version required to run the plugin in Visual Studio 2017 and 2019
was increased from .NET Framework 4.6 to .NET Framework 4.6.1. Version 4.6.1
or newer should already be installed if the latest Windows
and Visual Studio updates are present, so no changes should be necessary for plugin users.
The requirements for the plugin for Visual Studio 2022 and 2026 have not changed.
1.5.14.6. IR¶
The following IR classes were previously unused (the compiler did not create any nodes of these types) and have been removed in version 7.11:
ir.Physical.PCH_File
ir.Logical.Logical_Instruction
ir.Logical.And_Instruction
ir.Logical.Or_Instruction
The following classes in the Physical part were renamed:
Old name |
New name |
|---|---|
|
|
|
|
|
|
1.5.14.7. Parallelism¶
The behavior of the command-line switch -j across all tools has been slightly
altered to reduce the number of parallel processes and ensure sufficient memory for
each process; see section Default Parallelism for more
details.
1.5.14.8. Stylechecks¶
FaultDetection-UseAfterFree¶
By default, calls to undefined (external) functions are now assumed to use all passed pointer arguments. This may lead to new or changed findings: if a new finding is reported on a call to an external function, later (existing) findings along that path are suppressed.
The following rules are also affected, as they use FaultDetection-UseAfterFree internally:
MisraC-21.1,
MisraC2012-21.20,
MisraC2012-22.2,
MisraC2012-22.6,
MisraC2012Directive-4.1 (if
execute_checks_covered_in_other_rulesis enabled),MisraC++-0.3.1,
MisraC++2023-25.5.3,
MisraC++2023-6.8.1, and
To restore the old behavior, set the new option
report_read_pointer_args_in_calls_to_undefined (enabled by default) to false
for any of the affected rules.
StaticSemanticAnalysis¶
The following style checks now operate with greater precision when StaticSemanticAnalysis is activated and may report more or fewer findings, depending on the rule:
MisraC-14.1
MisraC2012-2.1
MisraC2012-17.11
MisraC2023-2.1
MisraC++-0.1.1
MisraC++-0.3.2
MisraC++2023-0.0.1
SecureCoding-5.2¶
The rule now also checks for double-free errors as described in ISO-TS-17961.