HNHacker News
TopNewBestAskShowJobs

AndreyKarpov

4,144 karma · joined February 11, 2011

Andrey Karpov. DevRel. Andrey Karpov is a co-founder of PVS-Studio — the company that is developing the PVS-Studio static code analyzer. The tool is designed for early detection of errors and potential vulnerabilities in C, C++, C#, and Java projects.

Andrey is the author of many publications devoted to writing quality C++ code.

Articles published in the company's blog: https://pvs-studio.com/en/blog/posts/?author=andrey-karpov

submissionscomments
AndreyKarpov··on 27000 errors in the Tizen operating system
The compiler warnings are good, but they are not enough :). Specialized tools for static analysis, such as PVS-Studio will always outpace the compilers in diagnostic capabilities and configuration flexibility working with false positives. That's actually how the analyzer developers make money. Proofs: https://www.viva64.com/en/inspections/#ID0EAPAG
AndreyKarpov··on 27000 errors in the Tizen operating system
> I read those posts regularly, but I don't remember them announcing any new features or improvements in PVS-Studio itself.

PVS-Studio Release History: https://www.viva64.com/en/m/0010/

PVS-Studio project - 10 years of failures and successes: https://www.viva64.com/en/b/0465/

How PVS-Studio does the bug search: methods and technologies: https://www.viva64.com/en/b/0466/

AndreyKarpov··on Free PVS-Studio Licenses to Security Experts
How Can PVS-Studio Help in the Detection of Vulnerabilities? - https://www.viva64.com/en/b/0514/
AndreyKarpov··on The Evil within operator ==
When you read it, please, don't run away. Please, return back and put a like. :) The article deserves to be known.
AndreyKarpov··on Bugs in Visual C++ 2017 Libraries
Annotation. The title of this article is a hint for the Visual Studio developers that they could benefit from the use of PVS-Studio static code analyzer. The article discusses the analysis results of the libraries in the recent Visual C++ 2017 release and gives advice on how to improve them and eliminate the bugs found. Read on to find out how the developers of Visual C++ Libraries shoot themselves in the foot: it's going to be interesting and informative.
AndreyKarpov··on Weaknesses detected by PVS-Studio this week: episode N4
P.S. PVS-Studio team is ready to do regular audit of your code: https://www.viva64.com/en/b/0493/
AndreyKarpov··on A new home for Google Open Source
Well, now PVS-Studio has more code to check and to entertain the readers with reports. :) About the analysis of various open source projects by PVS-Studio Team: https://www.viva64.com/en/inspections/
AndreyKarpov··on Weaknesses detected by PVS-Studio this week: episode N3
Episode 1 - https://www.viva64.com/en/b/0484/ Episode 2 - https://www.viva64.com/en/b/0487/
AndreyKarpov··on The last line effect explained
Well, mostly yes.
AndreyKarpov··on The last line effect explained
Try short variant :) - https://www.viva64.com/en/b/0260/ (The Last Line Effect)
AndreyKarpov··on Modern diagnostics tools for C++ applications
Valgrind (dynamic analysis): Good but Not Enough - https://www.viva64.com/en/b/0278/
AndreyKarpov··on UE4: Static Code Analysis with PVS-Studio (Part 6)
* Part 1 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-static-code-a...

* Part 2 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-part2/

* Part 3 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-part3/

* Part 4 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-part4/

* Part 5 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-part5/

* Part 6 - http://coconutlizard.co.uk/blog/ue4/pvs-studio-part6/

AndreyKarpov··on Recommendations about coding in C++
sal: add comment re: V718 'CreateThread' should not be called from 'DllMain'

http://opengrok.libreoffice.org/diff/core/sal/osl/w32/dllent...

AndreyKarpov··on Recommendations about coding in C++
I think they but downvote for this comment because this approach is not very sensible. There is no point to say "you should write well and without mistakes". Moreover there is no point to recommend rewriting everything in a different language - it is impossible for large projects.
AndreyKarpov··on Recommendations about coding in C++
The fact that these are simple errors doesn't mean that these are not errors. We should understand tat they are especially noticeable when there is a small code fragment. In the code of a real application such errors can live for years. By the way, I recommend playing: http://q.viva64.com/
AndreyKarpov··on Recommendations about coding in C++
I do not remember this comment. Most likely he appeared after the article: http://www.viva64.com/en/b/0308/
AndreyKarpov··on New Linux Kernel Bugs by PVS-Studio Team
Most of all I like this:

char *stime[] = { "400ms", "5min", "10min", "15min", "20min", "25min", "30min" "No timeout" };

AndreyKarpov··on PVS-Studio static code analyzer for C, C++ and C#: the cases for Free use
And LLVM too :) http://www.viva64.com/en/b/0446/
AndreyKarpov··on PVS-Studio VS Microsoft Open Source Code
C++ bugs

* Check of CNTK - http://www.viva64.com/en/b/0372/

* Check of ChakraCore - http://www.viva64.com/en/b/0370/

* Check of CoreCLR - http://www.viva64.com/en/b/0310/

* Check of Windows 8 Driver Samples - http://www.viva64.com/en/b/0199/

* Check of Microsoft Word 1.1a - http://www.viva64.com/en/b/0245/

* Check of Visual C++ libraries: 1 - http://www.viva64.com/en/b/0163/ , 2 - http://www.viva64.com/en/b/0288/

* Check of Casablanca - http://www.viva64.com/en/b/0189/

C# bugs

* Check of PowerShell - http://www.viva64.com/en/b/0447/

* Check of CoreFX - http://www.viva64.com/en/b/0365/

* Check of .Net Compiler Platform (Roslyn) - http://www.viva64.com/en/b/0363/

* Check of Code Contracts - http://www.viva64.com/en/b/0361/

* Check of MSBuild - http://www.viva64.com/en/b/0424/

* Check of WPF Samples - http://www.viva64.com/en/b/0407/).

AndreyKarpov··on We continue checking Microsoft open source projects: analysis of PowerShell
From "PVS-Studio for Linux" - http://www.viva64.com/en/b/0441/

The new Linux version (.deb, .rpm, .tgz) is available for download on the page:

http://www.viva64.com/en/pvs-studio-download-linux/

We also recommend reading the documentation section "How to run PVS-Studio on Linux" http://www.viva64.com/en/pvs-studio-download-linux/ . If something is not clear or something does not work, we will gladly help you, feel free to ask questions in the mail.

If you want to get a registration key to try out the tool - contact us http://www.viva64.com/en/about-feedback/ . Over the time the process of getting the trial version may change, but now it is important for us to understand who downloads the analyzer, how the person uses it and which issues appear during the usage.

AndreyKarpov··on We continue checking Microsoft open source projects: analysis of PowerShell
PVS-Studio user review: PVS-Studio C# - https://jackmott.github.io/programming/2016/11/01/PVS-Studio...
AndreyKarpov··on We continue checking Microsoft open source projects: analysis of PowerShell
For information, I wanted to point out that PVS-Studio is able to integrate with SonarQube: http://www.viva64.com/en/m/0037/
AndreyKarpov··on Bugs found in GCC with the help of PVS-Studio
Java
AndreyKarpov··on Bugs found in GCC with the help of PVS-Studio
Not yet. We are now experimenting with C# support and with Linux support. What's next, we do not know yet. There are two perspective areas: Objective-C and Java.
AndreyKarpov··on Bugs found in GCC with the help of PVS-Studio
Yes. No relationship. PVS: OOO "Program Verification Systems" (Co. Ltd.)
AndreyKarpov··on Bugs found in GCC with the help of PVS-Studio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77421
AndreyKarpov··on CryEngine bugs
Customers: http://www.viva64.com/en/customers/

John Carmack: https://twitter.com/ID_AA_Carmack/statuses/22680046289094656... and https://twitter.com/ID_AA_Carmack/statuses/25894050786931097...

AndreyKarpov··on Let's Play a Game – find bugs in popular open-source projects
> I wonder what the costs are though - the quotes are hidden from their site.

You can easy try PVS-Studio. Explanation about the PVS-Studio demo-version limitations: http://www.viva64.com/en/b/0395/

> You cannot simply spend a year fixing bugs no-one actually cares about (because software was working well enough before).

Yes. You can analysis only newly written code. Best Practices of using PVS-Studio. Now with C# support: http://www.viva64.com/en/b/0364/

AndreyKarpov··on Let's Play a Game – find bugs in popular open-source projects
C#... huh :)

Accord.Net - http://www.viva64.com/en/b/0410/

Microsoft WPF Examples - http://www.viva64.com/en/b/0407/

Xamarin.Forms - http://www.viva64.com/en/b/0400/

Lucene.Net - http://www.viva64.com/en/b/0381/

Xenko Game Engine - http://www.viva64.com/en/b/0379/

Space Engineers - http://www.viva64.com/en/b/0376/

WPF examples by the Infragistics Company - http://www.viva64.com/en/b/0375/

CNTK tool kit - http://www.viva64.com/en/b/0372/

Sony C#/.NET component - http://www.viva64.com/en/b/0371/

IronPython and IronRuby - http://www.viva64.com/en/b/0367/

MonoDevelop - http://www.viva64.com/en/b/0366/

CoreFX - http://www.viva64.com/en/b/0365/

Roslyn - http://www.viva64.com/en/b/0363/

AndreyKarpov··on Let's Play a Game – find bugs in popular open-source projects
But: PVS-Studio Probes into Linux' Innards - http://www.viva64.com/en/b/0299/
← PreviousPage 2 of 5Next →