Delve Debugger VS Clang Static Analyzer

At a recent job, we had slightly different containers for local dev; our backend containers (for a Go app) had Air [1] installed for live reloading, plus Delve [2] running inside the container for VS Code's debugger to connect to. We also had a frontend container for local dev, which didn't get deployed as a container, just as static files. [1] https://github.com/cosmtrek/air. - Source: Hacker News / 5 months ago

So in my case I use https://github.com/leoluz/nvim-dap-go (which itself calls out to the CLI tool https://github.com/go-delve/delve). Source: about 1 year ago

I usually set up a scratch-pad module on my machines for quickly throwing some code together to play with. For debugging/checking attributes etc. there's delve, which is usually built in to various editor's respective Go plugin. Source: over 1 year ago

I use a debugger every day. Delve[0] Go's debugger made me love the process of debugging my code – either attaching the debugger to an existing running process or the feedback loop of debugging the test code until make it passes the test case. Back in the days when I didn't use one, it was a miserable developer experience. Thanks to Go and his great decision of having unit testing built into their standard now... - Source: Hacker News / over 1 year ago

The required setup to debug a Go app running inside a Docker container is non-trivial. In this post I will walk through the configuration to achieve this using VSCode and the Delve debugger. - Source: dev.to / 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