Splint VS Delve Debugger

Whenever I see people talk about the portability or compatibility advantages of C, I'm reminded of how "even C isn't compatible with C", because you typically aren't talking about up-to-date GCC or LLVM on these niche platforms... you're talking about some weird or archaic vendor-provided compiler... Possibly with syntax extensions that static analyzers like splint will choke on. (Splint can't even understand near... Source: about 1 year ago

Huh. I think I actually needed to use the equivalent position for certain splint annotations in my C retro-hobby project. Source: about 1 year ago

I often like to say that Rust's bindings are a way to trick people into writing the compile-time safety annotations that they didn't want to write for things like splint. (Seriously. Look into how much splint is capable of checking with the correct annotations.). Source: over 1 year ago

Linters like Splint [0] can do that for C. I’m not saying that Rust’s built-in approach isn’t better, but please be careful about what exactly you claim. [0] http://splint.org/. - Source: Hacker News / over 1 year ago

(Sort of like how, for my DOS hobby project, I use splint to require explicit casts between typedefs so I can use the newtype pattern without having to manually reach into wrapper struct fields in places that don't do conversions.). Source: almost 2 years ago

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: over 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