Pour obtenir une clé
d'essai remplissez le formulaire ci-dessous
Demandez des tariffs
Nouvelle licence
Renouvellement de licence
--Sélectionnez la devise--
USD
EUR
RUB
* En cliquant sur ce bouton, vous acceptez notre politique de confidentialité

Free PVS-Studio license for Microsoft MVP specialists
To get the licence for your open-source project, please fill out this form
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

I am interested to try it on the platforms:
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

Votre message a été envoyé.

Nous vous répondrons à


Si vous n'avez toujours pas reçu de réponse, vérifiez votre dossier
Spam/Junk et cliquez sur le bouton "Not Spam".
De cette façon, vous ne manquerez la réponse de notre équipe.

>
>
Integrating PVS-Studio into Anjuta DevS…

Integrating PVS-Studio into Anjuta DevStudio (Linux)

06 Déc 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
I want to use PVS-Studio in my project. The manager is against it. How to convince them?

Date: 02 Aoû 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 ob…
How PVS-Studio for Windows got new monitoring mode

Date: 14 Jui 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: 19 Avr 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 go…
What's new in PVS-Studio in 2021?

Date: 31 Déc 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!
VSCode: how to view reports of static analyzers that support SARIF

Date: 09 Aoû 2021

Author: Nikolay Mironov

People increasingly start optimizing the process of finding code errors using static analyzers. Nowadays, we can choose from a variety of products to view analysis results. This post covers the ways …

Comments (0)

Next comments
Unicorn with delicious cookie
Nous utilisons des cookies pour améliorer votre expérience de navigation. En savoir plus
Accepter