memcheck

I don't see a lot of programmers trying to run diskcheck or memcheck every time they have an unexplainable crash.

Write a MemCheck hook and generate all the metrics you want.

UB has the benefit that there are a lot of tools like valgrind, memcheck, and various compiler features to detect it both statically and at runtime.

I typically run my C projects' test suites through Valgrind memcheck and fix all errors, leaks, and still-reachables before releasing any new versions.

They didn't use a real memory access checker like valgrind even to load a blank page, although they came up with a weaker memcheck that mostly works.

Valgrind (memcheck) is not just a leak detection tool.

I’m not aware of many memcheck bugs that aren’t relatively obscure corner cases.

Valgrind(-memcheck) is an extremely important tool in memory-unsafe languages.

I've used Valgrind (mainly memcheck) as a proactive tool or at least as a tool to fish for easy to fix issues before spending too much time debugging specific reports.

So I think that being always context specific (ie in this case I need memcheck, in the other case I don't use C at all so it is a useless skill) is too deep.

And then there are the valgrind tools other than memcheck: cachegrind (cache and branch-prediction profiler), callgrind (call-graph profiler), helgrind (thread error detector), massif (heap profiler), and probably more I forget.

It looks like if you want the memcheck functionality on the client, memcheck.js must be distributed with your "compiled" javascript code.

Memcheck (the main tool) has shortcomings (very slow, does not detect all kinds of errors).

The main things that Memcheck, the default Valgrind tool, do are: 1.

See: $ valgrind./a.out ==5118== Memcheck, a memory error detector ==5118== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.