Examples of using Compiler monitoring in English and their translations into Russian
{-}
-
Official
-
Colloquial
Such a scenario is natural for the Compiler Monitoring system.
Compiler monitoring is first launched with CLMonitor. exe.
Command line utility for PVS-Studio Compiler Monitoring System is not available.
In addition, regardless of the build system being utilized,you can use PVS-Studio compiler monitoring system.
To learn more about the use of the compiler monitoring system, see this documentation section.
Because of that, just for cases like this, we created a compiler call"intercepting" system- Compiler Monitoring.
You can check any project by using the compiler monitoring mode from Standalone tool.
Compiler Monitoring system is described in more detail in the article" Compiler Monitoring System in PVS-Studio.
As an example, let's review the integration of PVS-Studio analysis through compiler monitoring into a makefile project.
To learn more about the use of the compiler monitoring system, see the article" Compiler Monitoring System in PVS-Studio.
Direct integration may be necessary when you cannot use the command line module'PVS-Studio_Cmd. exe' and the compiler monitoring system see the note in the corresponding section.
To do the analysis we also used the compiler monitoring system, which allows to do the project analysis no matter what system is used to build this project.
In case of necessity of performing the incremental analysis when using the Compiler Monitoring system, it is enough to"monitor" the incremental build, i.e.
If this is the case, you can use the compiler monitoring system that allows you to analyze projects regardless of the build systems they use by"intercepting" compilation process invocations.
The Compiler Monitoring system can"intercept" compilation process launches, collecting all of the parameters necessary for successful preprocessing, thenre-launch preprocessing for files under compilation for further analysis.
This monitoring system consists of a compiler monitoring server(the command-line utility CLMonitor. exe) and an UI client integrated into the Standalone version of PVS-Studio and responsible for launching the analysis.
The compiler monitoring system has a number of drawbacks stemming from the natural limitations of this approach, namely the impossibility to guarantee a 100% intercept of all the compiler launches during the build process.
As the name suggests, the Compiler Monitoring system is based on"monitoring" compiler launches when building a project, which allows the analyzer to gather all the information essential for analysis of the source files being built.
The PVS-Studio Compiler Monitoring system, or CLMonitoring, is designed to provide'seamless' integration of PVS-Studio into any build system under Windows that employs one of the preprocessors supported by the command line module'PVS-Studio. exe' for compilation.
The PVS-Studio Compiler Monitoring system(CLMonitoring) was designed for"seamless" integration of the PVS-Studio static analyzer into any build system under Windows that employs one of the preprocessors supported by the PVS-Studio. exe command-line analyzer for compilation.
It monitoring compiler calls and get all the necessary information.
Monitoring compiler launches and collecting all the information necessary for further analysis.
We can now monitoring all compiler launches and easily check the project.
The analysis was done with the help of the compiler call monitoring system of the Standalone utility coming with the PVS-Studio pack, as mentioned above.
The monitoring window indicated that the compiler calls were being tapped.
The rest of the analysis process is completely identical to the described above,in the section"Analyzing source files with the help of the compiler process monitoring system.
This utility employs the monitoring feature, which tracks compiler calls and passes all the necessary files to the analyzer.
If the monitoring server has successfully tracked the compiler invocations, static analysis will be launched for the source files.
If the monitoring server has successfully tracked all the compiler launches, the preprocessed files will be generated first and then they will be analyzed.
Note: for the monitoring server to run correctly, it must be launched with the same privileges as the compiler processes themselves.