Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #423

P

PVS-Studio

Company blog · viva64.com/en/bprogrammingsecurity

PVS-Studio is the company blog at viva64.com, writing about programming and security. Since 2011, 135 different Hacker News readers have linked it 1,021 times, most often “The Ultimate Question of Programming, Refactoring, and Everything”. No feed was found, so read it on the site itself.

1,021mentions?
9recommend?
135HN people?
2011–2021first – last linked?
Links on Hacker News per year · peak 164 in 2016

Sometimes recommended · 9 of 40 sampled comments recommend it?

Why HN links it

HN readers cite PVS-Studio's blog for C and C++ bug examples from real open-source projects, 32/64-bit porting errors and static analysis. Posts often serve as evidence in Rust versus C++ debates.

Recommended for · 9 comments
Called a very objective, in-depth article; a good summary of 64-bit porting issues; nice material on size_t; interesting reading on FreeBSD bugs; a nice paper; 12345678

Summarised by Claude from a sample of 40 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

A static analyzer for C, C++, C#, Java, Go, JavaScript and TypeScript code. Works on Windows, Linux, and macOS. Analyzes code for 32-bit, 64-bit, and ARM embedded platforms.

Most-linked posts?

  1. The Ultimate Question of Programming, Refactoring, and Everything
    10 people · 10 mentions · first linked 2016-04-14
  2. Criticizing the Rust Language, and Why C/C++ Will Never Die
    8 people · 8 mentions · first linked 2015-05-12
  3. C++ Bugs Library
    5 people · 11 mentions · first linked 2012-10-17
  4. PVS-Studio static code analyzer for C, C++ and C#: the cases for Free use
    5 people · 6 mentions · first linked 2016-11-30
  5. Rust Language, and Why C/C++ Will Never Die (2015)
    5 people · 5 mentions · first linked 2017-04-05
  6. PVS-Studio for Linux
    5 people · 5 mentions · first linked 2016-10-25
  7. Toyota: 81514 issues in the code, 89 people killed
    4 people · 5 mentions · first linked 2016-10-12
  8. /en/pvs-studio/
    4 people · 4 mentions · first linked 2017-07-13
  9. Counting Bugs in Windows Calculator
    4 people · 4 mentions · first linked 2019-03-12
  10. The Evil Within the Comparison Functions
    3 people · 6 mentions · first linked 2017-05-19

What Hacker News says?

  1. busterarm · 2018-01-13Recommends
    The best answer to "Rust hype" I've ever seen. https://www.viva64.com/en/b/0324/

    Comment linking /en/b/0324/

    on “An Experimental Course on Operating Systems”
  2. Submitted Bugs found in GCC with the help of PVS-Studio as a story · 186 points

    HN discussion
  3. The PVS-Studio Team couldn't get past the source code of this game: https://www.viva64.com/en/b/0707/

    Comment linking /en/b/0707/

    on “VVVVVV’s source code is now public, 10 year anniversary jam happening now”
  4. Submitted 27000 errors in the Tizen operating system as a story · 178 points

    HN discussion
  5. Checking Microsoft Word 1.1a with PVS-Studio. Just for fun. http://www.viva64.com/en/b/0245/

    Comment linking /en/b/0245/

    on “Microsoft makes source code for MS-DOS and Word for Windows available to public”
  6. Submitted The Last Line Effect as a story · 177 points

    HN discussion
  7. That's me schooled. I'd not been party to that (not being in the US) I'd missed it. http://www.viva64.com/en/a/0083/ It sounds like a proper mess. How curious that much is revealed that the NASA people didn't speak of. Maybe because it was ostensibly an investigation at the behest of NIHIST to demonstrate that they hadn't let Toyota off the hook. It is also somewhat disturbing that these are not Toyota parts but par…

    Comment linking /en/a/0083/

    on “Tesla Adds Titanium Underbody Shield and Aluminum Deflector Plates to Model S”
  8. Submitted Debunking that C++ is faster and safer than Rust as a story · 143 points

    HN discussion
  9. I agree it shouldn’t happen, but in this case, the programmer presumably made (more or less) the same mistake, writing out a variable called password unencrypted, possibly after copying it to a variable or structure field called passwordhint . Thinking of that, this may be an example of a copy-paste bug ( https://www.viva64.com/en/a/0068/ ), where the programmer wrote strcpy(&r.password , &encryptedpassword); strcpy…

    Comment linking /en/a/0068/

    on “If macOS High Sierra shows your password instead of the password hint”
  10. Submitted Why Don't Software Developers Use Static Analysis Tools to Find Bugs? as a story · 107 points

    HN discussion
  11. A Collection of Examples of 64-bit Errors in Real Programs: https://www.viva64.com/en/a/0065/

    Comment linking /en/a/0065/

    on “macOS Catalina”
  12. Submitted The Evil Within the Comparison Functions as a story · 104 points

    HN discussion
  13. I hate to suggest a web search but there are a lot of examples online if you search, e.g., https://www.viva64.com/en/a/0004/ One of the big ones is that integer constants are 32-bit on LP64 / LLP64 systems unless they are large enough, so e.g. // Equal to 0x80000000 on ILP32 // Undefined behavior on LP64 / LLP64 size_t max = 1u << (sizeof(size_t) * CHAR_BIT - 1); // Correct version size_t max = (size_t)1 << (sizeof(…

    Comment linking /en/a/0004/

    on “macOS Catalina”
  14. Submitted Can We Trust the Libraries We Use? as a story · 93 points

    HN discussion
  15. Good article! I read this article and was glad. I am pleased that we are moving in the right direction. We watched as our competitors sell Coverity ( http://www.coverity.com/ ) and Klocwork ( http://www.klocwork.com/ ). The process is very complicated. We ( http://www.viva64.com/ ) have avoided almost all of the items listed in the article. Cool.

    Comment linking /

    on “How Not To Sell Software in 2012”
  16. Submitted LibreOffice Project's Check as a story · 86 points

    HN discussion
  17. https://www.viva64.com/en/b/0324/

    Comment linking /en/b/0324/

    on “You can't Rust that”
  18. Submitted We continue checking Microsoft open source projects: analysis of PowerShell as a story · 83 points

    HN discussion
  19. My point is more like this chart [0]. C has so much lead time, Rust will probably never be able to catch up, be close? Sure. But C has decades of lead time. [0] http://www.viva64.com/media/images/content/b/0324_Criticizin...

    Comment linking /media/images/content/b/0324_Criticizing-Rust-Language-Why-Cpp-Will-Never-Die/image1.png

    on “A Generation Lost in the Bazaar (2012)”
  20. Submitted CppCat, an Ambitious C++ Code Analyzer from Tula as a story · 82 points

    HN discussion
  21. > Compared to /analyze, PVS-Studio is painfully slow, but... Tips on speeding up PVS-Studio - http://www.viva64.com/en/b/0126/

    Comment linking /en/b/0126/

    on “John Carmack on the importance of Static Code Analysis”
  22. Submitted Re-checking the ReactOS project - a large report as a story · 79 points

    HN discussion
  23. PVS-Studio vs Chromium - http://www.viva64.com/en/a/0074/ PVS-Studio vs Chromium - Continuation - http://www.viva64.com/en/b/0113/

    Comment linking /en/b/0113/

    on “John Carmack on the importance of Static Code Analysis”
  24. Submitted Criticizing the Rust Language, and Why C/C++ Will Never Die as a story · 78 points

    HN discussion
  25. I would say that the best economic value is being delivered if we consider some code fragments that are almost never covered by tests (any of them) - like error detector. Guys at pvs-studio brought in some pretty funny example of such errors: http://www.viva64.com/en/a/0078/

    Comment linking /en/a/0078/

    on “John Carmack on the importance of Static Code Analysis”
  26. Submitted Rust Language, and Why C/C++ Will Never Die (2015) as a story · 71 points

    HN discussion
  27. Having done similar work for Chrome, I can attest to the fact that large code bases are full of errors. If you're not on Windows, using both gcc's -Wall and -Wextra along with Clang in the same way is a good start. (Here's a post with more details: http://neugierig.org/software/chromium/notes/2011/01/clang.h... .) The Clang static analyzer wasn't very useful at the time I tried it because it didn't analyze C++ code.…

    Comment linking /en/b/0113/

    on “John Carmack on the importance of Static Code Analysis”
  28. Submitted The Last Line Effect as a story · 69 points

    HN discussion
  29. Checking ChakraCore with static analyzer: http://www.viva64.com/en/b/0370/

    Comment linking /en/b/0370/

    on “Enable Node.js to Run with Microsoft's ChakraCore Engine”
  30. Submitted The Quality of Embedded Software, or the Mess Has Happened as a story · 65 points

    HN discussion

Search all of HN for viva64.com

Linked by the same people?