Hacker News Reader

And valgrind!

That means building the code twice. In practice the only thing valgrind does that asan doesn't is checking for non-initialized variables. There's another sanitizer for this called msan.

Unfortunately not all of the sanitizers are working in clang for Apple Silicon machines. For my own CI pipeline I run both Darwin and Linux builds, leaks and valgrind respectively, along with the kitchen sink of compiler sanitizers:

Here’s the GitHub actions for those platforms and a link to the Makefile:

GitHub Action:

https://github.com/williamcotton/express-c/blob/master/.gith...

Makefile:

https://github.com/williamcotton/express-c/blob/f2e1dde2f5a7...

That's an interesting problem. Is this the case for all aarch64 platforms or is this specific to Apple's hardware?

valgrind runs on your unmodified binary, it's asan that needs a separate build.

The build you'd use for development, to run unit tests and validate merge requests, is the as-instrumented-as-possible build.

valgrind is too slow for day-to-day use. I only use it when I have something specific in mind.

I guess would be acceptible in CI pipeline too, but never tried.

Reply on news.ycombinator.com