rapgenic/vscode-valgrind

Valgrind dynamic analyser support for VSCode

vscode-valgrind's Issues

Documentation

• More detailed README
• Screenshots
• Examples how to run tools for generating a log

Rename to more generic memcheck tools

Handle path substitution for logs from other machines

Probably easy with valgrind as we can deduce it from the xml log file.

Don't know about the other tools... Possibilities:

• Duplicate command, one is normal, the other asks what path substitution should be made
• Keep a database of logfiles->applied substitutions to suggest again when necessary.

Investigate support for tools other than memcheck

Should be not too difficult: the XML format is quite well described, we should only need to add a few more branches in the parsing algorithm.

Populate default tasks that ask the executable to debug

If there is no task defined in the tasks.json file we should present a list of default tasks that ask the user for a executable to run.

Do not know if that is possible with vscode api.

Add heuristic to detect missing debug symbols

Better JSON schema for properties

• Should describe property dependencies (eg memcheck properties allowed only if tool is memcheck

Add compact mode

Group all the leaks of the same kind at the same line under the same diagnostic

Better parser

• Nodes are often mixed and fast-xml-parser doesn't like that
• Try xml2js

Add GitHub actions to build VSIX automatically

This will be useful in testing phase to deploy the extension easily