C++ code is fraught with perils and pitfalls. That's why a thorough and meticulous code review is very important. The purpose of this talk is to (hopefully) improve your ability to take on such a task. We'll take a look at some error patterns easily overlooked. In all honesty, many people just don't know about them. Meet a dangerous emplace_back, an unexpected integer overflow, a skipped memset, perils of noexcept functions, and so on.
Conference: Corehard 2019
It's a kind of humorous talk about the life of a development team which also deals with supporting C and C++ programmers. Actually, working with programmers is a lot of fun, and it is very productive. Not only can they send you a memory dump, but sometimes even partially solve the problem themselves and give you a hint. However, there's a flip side. If they have a technical issue, be ready to consume pints of coffee and loads of cookies. I shall tell you about our interesting and funny experience related to technical support of the PVS-Studio analyser - for example, how the tool goes nuts when coming across a 26mb string literal.
Conference: ClueCon Weekly
The video is on static code analysis and static code analyzer tool, which might be interesting for developers. It helps to search for potential flaws in code and finds various errors.
The report gives information about ways to detect bugs, methodology of static analysis, correct and incorrect use of analysis tools. The author also provides myths about static analysis that may lead to erroneous understanding among the developers. The presentation shows errors in Open Source projects, detected by such tools as ReSharper, PVS-Studio, Visual Studio SCA.