Skip to main content

Home/ Programming/ Group items tagged errors

Rss Feed Group items tagged

Andrey Karpov

PVS-Studio is a static code analyzer that scans C, C++ and C++11 code and highlights b... - 0 views

  •  
    PVS-Studio is a static analyzer that detects errors in source code of C/C++/C++11 applications. There are sets of rules included into PVS-Studio: General-purpose diagnosis Detection of possible optimizations Diagnosis of 64-bit errors (Viva64) Diagnosis of parallel errors (VivaMP)
Andrey Karpov

Errors detected in Open Source projects by the PVS-Studio developers through static ana... - 0 views

  •  
    We regularly check various open-source projects with PVS-Studio and send analysis results to developers and usually describe them in our posts as well. Besides, we add them into our bug database. This database is posted below on this page. The bugs are grouped according to the number of the diagnostic rule that is used to detect them. This number is given in the left column. Click on it to see the diagnostic rule description in the documentation. The right column contains a link to the corresponding error samples. Some diagnostics haven't detected any bugs in open-source projects yet. The lower you are in the list, the more diagnostics with no error samples there will be. The reason is simple: the later a certain rule had been added, the fewer projects were analyzed with this rule included into the rule set and therefore the fewer chances for it to demonstrate its capabilities.
yc c

CWE - 2010 CWE/SANS Top 25 Most Dangerous Programming Errors - 0 views

  • The 2010 CWE/SANS Top 25 Most Dangerous Programming Errors is a list of the most widespread and critical programming errors that can lead to serious software vulnerabilities. They are often easy to find, and easy to exploit. They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or prevent the software from working at all.
Andrey Karpov

PVS-Studio registration key for 5 days - 0 views

  •  
    As an experiment, we have decided to offer everyone interested a PVS-Studio registration key for 5 days to study its 64-bit diagnostics more thoroughly. The PVS-Studio demo version is absolutely full-function. It is sufficient to study the tool and get familiar with its capabilities. The user has up to 200 clicks to navigate through code fragments the analyzer considers to be probably incorrect. We believe it's quite enough for the user to decide if he/she likes the tool or not. However, that might be insufficient in case you are searching for 64-bit errors. Many of the 64-bit warnings are false positives or are irrelevant to this program, as fragments they point to cannot cause errors. That's why the restriction of 200 messages you can click to navigate through the code may prevent you from forming a definite opinion of the tool. We have been watching an increasing interest towards development of 64-bit software lately. Perhaps this has to do with the release of Embarcadero RAD Studio XE3 Update 1 that has learned now to compile 64-bit applications. Or maybe it's just that the time has come.
Andrey Karpov

A database of errors detected by PVS-Studio is available on our website - 0 views

  •  
    The best way to advertise a static code analyzer is to find errors in open source projects and share them with the world. We have been using this method for a long time while promoting our tool PVS-Studio. If you have ever heard of PVS-Studio, it was most likely from our articles reporting on the checks of such projects as Chromium, WinMerge, TortoiseSVN, Apache HTTP Server, Qt, Clang and many others.
yc c

JSHint, A JavaScript Code Quality Tool - 4 views

  •  
    JSHint is a tool to detect errors and potential problems in JavaScript code.
Andrey Karpov

The Ultimate Question of Programming, Refactoring, and Everything - 0 views

  •  
    Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The author is Andrey Karpov - technical director of "Program Verification Systems", a team of developers, working on PVS-Studio static code analyzer. Having checked a large number of open source projects, we have seen a large variety of ways to shoot yourself in the foot; there is definitely much to share with the readers. Every recommendation is given with a practical example, which proves the currentness of this question. These tips are intended for C/C++ programmers, but usually they are universal, and may be of interest for developers using other languages.
Andrey Karpov

The compiler is to blame for everything - 0 views

  •  
    Many programmers are very fond of blaming the compiler for different errors. Let's talk about it.
Andrey Karpov

The D language comes to help - 0 views

  •  
    My name is Andrey Karpov. I develop software for developers, and I'm fond of writing articles on code quality issues. In this connection, I have met the wonderful man Walter Bright who has created the D language. In the form of an interview, I will try to learn from him how the D language helps programmers get rid of errors we all make when writing code.
Andrey Karpov

All about PVS-Studio - 0 views

  •  
    PVS-Studio is a static analyzer that detects errors in source code of C/C++/C++11 applications. The PVS-Studio tool integrates into the Visual Studio 2005/2008/2010 environment.
Andrey Karpov

Static analysis should be used regularly - 0 views

  •  
    We have a practice of occasionally re-analyzing projects we have already checked with PVS-Studio. There are several reasons why we do so. For example, we want to know if we have managed to eliminate false positives for certain diagnostics. But the most interesting thing is to see how new diagnostic rules work and what errors they can find. It is very interesting to watch the tool catch more and more new defects in a project that seems to be cleaned out already. The next project we have re-checked is Clang.
Andrey Karpov

Why Windows 8 drivers are buggy - 0 views

  •  
    We have checked the Windows 8 Driver Samples pack with our analyzer PVS-Studio and found various bugs in its samples. There is nothing horrible about it - bugs can be found everywhere, so the title of this article may sound a bit high-flown. But these particular errors may be really dangerous, as it is a usual practice for developers to use demo samples as a basis for their own projects or borrow code fragments from them.
yc c

About Query Editor - Freebase - 0 views

  • Syntax Tolerance MQL, which has JSON syntax, is not so hard to write, but sometimes you can make minor syntax mistakes that renders your query invalid. The query editor automatically tries to clean up such syntax errors behind the scene before running the query, so that you can still make mistakes, such as forgetting quotation marks and commas (illustrated in screenshot below), and your query still runs most of the time. You can also tell the query editor to explicitly clean up your query by clicking the Clean Up button. It will quote unquoted strings and property names, insert missing commas, and remove trailing commas. (Tip: the keyboard shortcut Shift-Ctrl-Enter will clean up your query explicitly and then run it.)
  •  
    Experiment with ways to get data out of Freebase using our JSON-based query language. 
1 - 13 of 13
Showing 20 items per page