Our website uses cookies to enhance your browsing experience.
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Integrating PVS-Studio into Anjuta DevS…

Integrating PVS-Studio into Anjuta DevStudio (Linux)

Dec 06 2016

When PVS-Studio for Linux was released, I tried it on my project and thought it would make a good supplement to other analyzers that I'd already been using.

Note. This article was originally published in Russian on habrahabr.ru. The original and translated versions are posted on our website with the permission of the author.

Since the astrologers have announced an "Integrate PVS-Studio into your favorite IDE" week, I decided to write a small post about my experience of setting up Anjuta DevStudio tool (http://anjuta.org/) to work with the analyzer. Many thanks to Vsevolod Lutovinov for the script he shared and his article Integrating PVS-Studio into Eclipse CDT (Linux) ("Integrating PVS-Studio into Eclipse CDT (Linux)")

I took the script from the original article and slightly modified it to work with projects built with autotools.



# without arguments, the script is called as External Tool,
# and we need to call 'make clean' forcedly:
if [ -z "$1" ]; then
    make clean

# calling from the builder, checking the targets:
if [ "$2" = "clean" ]; then
    make clean
   # we're done here:

# no 'clean' or the script is called as External Tool -
# start analysis: 

# cleaning up leftovers of 'strace' that may appear in certain cases:
pvs-studio-analyzer trace -- make 2>&1 | sed '/strace: umovestr:/d' -
pvs-studio-analyzer analyze -o "$TEMPLOG"

# removing the obscure line that I get in the converter's output:
RC=$(plog-converter -t errorfile "$TEMPLOG" \
    | sed '/The documentation for all/d' -)
rm -f "$TEMPLOG"
echo "$RC"

After that, open the project you want to check and go to Preferences. In General, switch to the "Installed Plugins" tab and tick the "Tools" plugin.


Figure 1 - Anjuta Preferences: Tools

Scroll to the end of the preferences list to the "Tools" option and add a new tool, "PVS-Studio Check".


Figure 2 - Tools

Set the tool as shown below


Figure 3 - Tool Editor

Once you've set it up, click on the "PVS-Studio Check" command of the "Tools" menu to start analysis and have the analyzer warnings output in the standard message window. Double-clicking on a warning will take you to the corresponding line.


Figure 3 - Example

Popular related articles
DefectDojo and PVS-Studio: tracking errors and vulnerabilities

Date: Aug 15 2023

Author: Mikhail Evtihevich

How to simplify the process of bug fixing and prevent vulnerable code from being released? Use quality control tools. We will use PVS-Studio to search for errors and vulnerabilities, and DefectDojo...
I want to use PVS-Studio in my project. The manager is against it. How to convince them?

Date: Aug 02 2022

Author: Sergey Vasiliev

You decided to integrate PVS-Studio into your project. But suddenly it turns out that the manager is against it, because... because why, actually? Let's try to figure out what to do with potential...
How PVS-Studio for Windows got new monitoring mode

Date: Jun 14 2022

Author: Alexey Govorov

In PVS-Studio 7.18, the compiler monitoring utility for Windows got new mechanism that completely eliminates missed compiler launches. In this article, we will remind you how our analyzer copes with.…
SAST in Secure SDLC: 3 reasons to integrate it in a DevSecOps pipeline

Date: Apr 19 2022

Author: Sergey Vasiliev

Vulnerabilities produce enormous reputational and financial risks. That's why many companies are fascinated by security and desire to build a secure development life cycle (SSDLC). So, today we're...
What's new in PVS-Studio in 2021?

Date: Dec 31 2021

Author: Maxim Stefanov, Oleg Lisiy, Sergey Vasiliev

2021 is coming to an end, which means it's time to sum up the year! Today we'll tell you about the new features we added to PVS-Studio in the past year. Buckle up and let's go!

Comments (0)

Next comments next comments
close comment form