Dr. Memory
Valgrind
WinAPIOverride
Deleaker
Relyze WonderLeak
API Monitor
SonarQube
perf
Clang Static Analyzer
Cppcheck
SonarQube
Coverity Scan
Parasoft C/C++test
lgtm.com
PVS-Studio
LDRA Testbed
Dr. MemoryDr. Memory might be a bit more popular than Clang Static Analyzer. We know about 9 links to it since March 2021 and only 7 links to Clang Static Analyzer. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I look forward to trying this out. It might be a good test-case; this codebase is so convoluted it has actually triggered internal crashes in some analysis tools I've tried on it. For example starting the application under Dr. Memory (https://drmemory.org/) results in a hung process. Source: 10 months ago
Profiling the game and looking at what time is spent on during the freezes is a start. Checkout https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/event-tracing-for-windows--etw- / https://drmemory.org/. Source: about 1 year ago
Yes, you can use Dr. Memory, works out of the box on windows with mingw and visualcpp. Source: about 1 year ago
Other, heavier, tools exist to the same affect that work cross platform - Dr. Memory being my preference. Source: over 1 year ago
I like to use Dr. Memory - excellent Valgrind alternative for Windows users. Source: almost 2 years ago
Clang has a similar tool, the Clang Static Analyzer: https://clang-analyzer.llvm.org/. - Source: Hacker News / about 1 month ago
Continuous Integration and Continuous Deployment [CI/CD] pipelines play a crucial role in enforcing code quality, especially when working with memory-unsafe languages. By integrating automated dynamic analysis tools like Valgrind or AddressSanitizer, static analysis tools like Clang Static Analyzer or cppcheck, and manual code review processes, developers can identify and mitigate many memory-related... - Source: dev.to / about 1 month ago
No one static analyzer catches everything. It's best to run multiple. Popular ones are cppcheck, clang-analyzer, GCC static analyzer in GCC 10+, flawfinder, lizard. Source: about 1 year ago
With "cross translation units" (CTU) analysis a static analyzer could derive a constraint on `some_function` return value and check this against the array size to detect a possible bug. The Clang static analyzer [1], used through CodeChecker (CC) [2], do support CTU (enabled with `--ctu`). I'm very happy with the result on the code I'm working on. Of course this is not magic, and it's important to understand the... - Source: Hacker News / over 1 year ago
Cppcheck and Clang Analyzer: statically analyze your code to find bad style and bugs (undefined behavior) respectively. Clang Analyzer can actually be frighteningly clever and has a low false positive rate (unlike most other non-commercial static checkers). Source: almost 2 years ago
Valgrind - Valgrind is an instrumentation framework for building dynamic analysis tools.
Cppcheck - Cppcheck is an analysis tool for C/C++ code. It detects the types of bugs that the compilers normally fail to detect. The goal is no false positives. CppCheckDownload cppcheck for free.
WinAPIOverride - WinAPIOverride : This software allows you to monitor and/or modify any function of a process for any calling convention (stdcall or cdecl)
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
Deleaker - Deleaker finds memory leaks, GDI leaks, leaks of handles, USER objects and others. Available both as a Visual C++ extension and standalone application.
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free