This is a proposal to move valgrind support into the warnings-ng plugin. Currently it's available in the semi-unmaintained valgrind plugin, but I think the warnings plugin would be a good fit:
- Valgrind provides stacktraces where an error occurs. It would be nice to link these to source files.
- The warnings-ng plugin would need a good way to visualize stack traces, I think this would be useful to many languages.
- This sort of fits into the idea of warnings-ng handling lots of different report formats, of which valgrind would just be another.
This is just an outline of an idea.