Our website uses cookies to enhance your browsing experience.
Accept
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--
USD
EUR
* 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 do not see the email in your inbox, please check if it is filtered to one of the following folders:

  • Promotion
  • Updates
  • Spam

>
>
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.

pvs-anjuta.sh

#!/bin/sh

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

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

# no 'clean' or the script is called as External Tool -
# start analysis: 
TEMPLOG=$(tempfile)

# 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.

0459_Anjuta_DevStudio/image1.png

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".

0459_Anjuta_DevStudio/image3.png

Figure 2 - Tools

Set the tool as shown below

0459_Anjuta_DevStudio/image5.png

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.

0459_Anjuta_DevStudio/image6.png

Figure 3 - Example

Popular related articles


Comments (0)

Next comments next comments
close comment form