Top 10 errors in C and C++ projects in 2023

By Andrey Karpov | Dec 22, 2023 05:26 AM | Tags: pvs-studio

New Year is coming! It means, according to tradition, it's time to recall 10 of the most interesting bugs that PVS-Studio found during 2023.

Top 10 errors in C and C++ projects in 2023

by Alexey Gorshkov

From the article:

In this case, the developers wanted to fill the keyEventList array with zeros. Pay attention to the third parameter — the number of bytes the developers wanted to fill with zeros. In this case, sizeof(keyEventList) evaluates the pointer size instead of the array size. It depends on the target platform, but most often it's 4 or 8 bytes. However, the size of the structure is clearly larger than 4 or 8 bytes.

SObjectizer Tales – 11. Interlude: testing--Marco Arena

By Marco Arena | Dec 21, 2023 06:28 AM | Tags: sobjectizer intermediate c++20

A new episode of the series about SObjectizer and message passing:

SObjectizer Tales – 11. Interlude: testing

by Marco Arena

From the article:

In this episode we discuss how to test message passing-styled applications and we'll add some unit and integration tests to our project.

Helping open communities thrive - Lydia Pintscher - Center Keynote Meeting C++ 2023

By Meeting C++ | Dec 20, 2023 12:47 PM | Tags: meetingcpp keynote community

Lydia Pintscher of KDE and Wikimedia gave a great community focused keynote at Meeting C++ 2023

Helping open communities thrive - Lydia Pintscher - Center Keynote Meeting C++ 2023

by Lydia Pintscher

 

How Can I Prevent Myself From Using a Parameter After I’ve Extracted All Value? -- Raymond Chen

By Blog Staff | Dec 18, 2023 04:27 PM | Tags: None

Imagine you have a function parameter that you want to protect from direct access, ensuring that all future interactions occur through a wrapper or transformation. This situation often arises in scenarios like implementing a logging wrapper for a class. In this discussion, we'll explore a clever technique known as "hide_name" to achieve this goal, allowing you to enforce the use of the wrapper and prevent direct access to the parameter.

How Can I Prevent Myself From Using a Parameter After I’ve Extracted All Value From It?

By Raymond Chen

From the article:

Suppose you have a function that takes a parameter that you want to transform in some way, and you want to require that all future access to the parameter be done through the transformed version. One example is a wrapper class that does logging.¹

struct WidgetRefWrapper
{
    WidgetRefWrapper(
        Widget& widget,
        Logger& logger) :
    m_widget(widget), m_logger(logger) {}
    
    void Toggle() try
    {
        m_logger.Log("Toggling the widget");
        m_widget.Toggle();
        m_logger.Log("Toggled the widget");
    } catch (...) {
        m_logger.Log("Exception while toggling the widget");
        throw;
    }

private:
    Widget& m_widget;
    Logger& m_logger;
};

void DoSomething(Widget& widget)
{
    Logger& logger = GetCurrentLogger();
    WidgetWrapper wrapper(widget, logger);

    // Do not use the widget directly!
    // Always use the wrapper!

    if (needs_toggling) {
        wrapper.Toggle();
    }
}

You want that “Do not use the widget directly!” comment to have some teeth. Can you “poison” the widget parameter so it cannot be used any more?

PVS-Studio 7.28: support for ARM, analysis of Unreal Engine projects without Unity Build, and more

By Andrey Karpov | Dec 18, 2023 02:18 AM | Tags: unrealengine unreal engine sast sarif pvs-studio arm

Now you can run the analyzer on the ARM architecture, analyze .NET 8 projects, and check Unreal Engine projects without Unity Build — and there is more to come.

PVS-Studio 7.28: support for ARM, .NET 8, analysis of Unreal Engine projects without Unity Build, and more

by Gleb Aslamov

From the article:

When analyzing Unreal Engine projects with PVS-Studio, we often encounter issues with high memory usage and analysis slowdown. They usually arise when individual translation units are combined into a single file (the Unity Build system). Although the merging of translation units may have a positive impact on the compilation time, the large file size may increase the resource requirements for analysis.

6 impossible things - Kevlin Henney - Opening Keynote Meeting C++ 2023

By Meeting C++ | Dec 17, 2023 02:24 PM | Tags: meetingcpp intermediate advanced

Kevlin Henney gave the opening keynote at Meeting C++ 2023

6 impossible things - Kevlin Henney - Opening Keynote Meeting C++ 2023

by Kevlin Henney

Video:

2023-12 Mailing Available

By Administrator | Dec 16, 2023 06:04 PM | Tags: None

The 2023-12 mailing of new standards papers is now available.

SObjectizer Tales – 10. Handling GUI from main--Marco Arena

By Marco Arena | Dec 14, 2023 02:04 AM | Tags: sobjectizer intermediate c++20

A new episode of the series about SObjectizer and message passing:

SObjectizer Tales – 10. Handling GUI from main

by Marco Arena

From the article:

In this episode, we discuss how to test message passing-styled applications and provide some examples on our project.

Striving For Better C++ Code, Part I: Data Flow Analysis Basics -- Anastasia Kazakova

By Blog Staff | Dec 11, 2023 04:28 PM | Tags: None

We’ll look at the basics of data flow analysis, including how it works in general, while presenting several real-world examples where it can help you write better code.

Striving For Better C++ Code, Part I: Data Flow Analysis Basics

by Anastasia Kazakova

From the article:

All data flow inspections rely on the control-flow graph. This is a graph on which vertices are the statements in the program and edges are the control flow jumps between these statements (direct code execution, conditional jumps, loops, breaks, gotos, etc.).

For example, the control-flow graph at the right represents the function foo on the left:

SObjectizer Tales – 9. Splitting work--Marco Arena

By Marco Arena | Dec 7, 2023 01:28 AM | Tags: sobjectizer intermediate c++20

A new episode of the series about SObjectizer and message passing:

SObjectizer Tales – 9. Splitting work

by Marco Arena

From the article:

In this episode we'll delve into the fundamental way for dividing a task among several agents.