Group items matching

in title, tags, annotations or url

This presentation looks at PVS-Studio static code analyzer. PVS-Studio is a tool for bug detection in the source code of programs, written in C, C++ and C#. It works in Windows and Linux environment. PVS-Studio performs static code analysis and generates a report that helps a programmer find and fix bugs also performs a wide range of code checks, it is also useful to search for misprints and Copy-Paste errors.

"An Open Source C++ GUI library."

Required backend developer now drop your cv here https://www.owcareers.com/cv-drop-zone

WsCube Tech CPP quiz section helps you to build your technical skills in CPP programing language which based on oops concept

Cppcheck is a static analyzer for C and C++ code. It is open-source, free, cross-platform and easy-to-use. The project's website: http://Cppcheck.sourceforge.net/ Cppcheck is an open-source, free tool distributed under the GNU General Public License. Daniel Marjamäki is the project's author (his profile on StackOverflow). The project's source code can be downloaded from the github website.

Aliasing can cause paradoxical behavior.

This page is a collection of obscure C++ features, gathered over the years as I've explored different corners of the language. C++ is very big and I'm always learning more about it. Hopefully you'll learn something from this page even if you already know C++ pretty well. The features below are roughly ordered from least to most obscure.

Program errors occurring while porting C++ code from 32-bit platforms on 64-bit ones are observed. Examples of the incorrect code and the ways to correct it are given. Methods and means of the code analysis which allow to diagnose the errors discussed, are listed.

I've been working with the new features of C++11 for many months as I write a book on TDD in C++. The updates to the language make for a far-more satisfying experience, particularly in terms of helping me write clean code and tests.

I usually try to write these blogposts in a way that is readable for most game developers and enthusiasts, but today for a change I'd like to dive deep into a detail of C++: why sometimes the this pointer can differ even though it is being used within the same object.

This time I want to speak on the 'printf' function. Everybody has heard of software vulnerabilities and that functions like 'printf' are outlaw. But it's one thing to know that you'd better not use these functions, and quite the other to understand why. In this article, I will describe two classic software vulnerabilities related to 'printf'. You won't become a hacker after that but perhaps you will have a fresh look at your code. You might create similar vulnerable functions in your project without knowing that. STOP. Reader, please stop, don't pass by. You have seen the word "printf", I know. And you're sure that you will now be told a banal story that the function cannot check types of passed arguments. No! It's vulnerabilities themselves that the article deals with, not the things you have thought. Please come and read it.

We develop a static analyzer called PVS-Studio. This is a code analyzer capable of detecting errors in C/C++ software. When we communicated with you, I must have told you that this analyzer detects 64-bit errors and integrates only into the Visual Studio environment.

"Program Verification Systems" (Co.Ltd) has announced the release of the new major version of PVS-Studio 5.0. The utility performs static analysis of a source code to reveal coding errors, programmer´s mistakes, fragments of code that can potentially produce a bug or disrupt the logic of the program. The new version is announced to support C++Builder, Windows Phone 8 and Windows Store projects. Read more: http://sdt.bz/37360#ixzz2JZowL8RN Follow us: @sdtimes on Twitter | sdtimes on Facebook

There is no fragment in program code where you cannot make mistakes. You may actually make them in very simple fragments. While programmers have worked out the habit of testing algorithms, data exchange mechanisms and interfaces, it's much worse concerning security testing. It is often implemented on the leftover principle. A programmer is thinking: "I just write a couple of lines now, and everything will be ok. And I don't even need to test it. The code is too simple to make a mistake there!". That's not right. Since you're working on security and writing some code for this purpose, test it as carefully!

Database of errors detected by PVS-Studio (V501)