- Support passing additional flags to valgrind via the
VALGRINDFLAGSenv var - Accept more Valgrind XML output (leading to fewer panics)
- Update dependencies including a fix for a vulnerability in
regex(which didn't affect this crate, though)
- rework continuos integration tests and automate release workflow
- Update dependencies
- Support absence of
xwhatin valgrind XML output
- Check, if valgrind is installed and print a helpful error if not
- Handle other valgrind errors more gracefully
- Add a custom panic hook, that points the user to the bug-tracker
- Format help and panic messages depending on the terminal size
Breaking API and CLI change!
- Support running every
cargoexecutable (binary, unit tests, doctests, ...) - changed command line
cargo valgrind->cargo valgrind runcargo valgrind --tests->cargo valgrind testcargo valgrind --example asdf->cargo valgrind run --example asdf- etc.
- currently no valgrind parameter support
- Support user flags for the analyzed binary.
- Updated dependencies
- Better error message if valgrind is not found
- support multiple feature flags, similar to normal
cargo - support comma separation of features, similar to normal
cargo - Bugfix: replace
-by_in integration test target names
- Support running of integration tests (normal tests are not yet supported)
- Fixed panic if the crate under test contains a build script
- Print an error if there are no runnable targets available
- Support the valgrind parameter
--show-leak-kinds=<set> - Support the valgrind parameter
--leak-check=<summary|full>
- Manually implement
HashforTarget. This was previously derived, which was wrong due to the customPartialEq-implementation (refer to theHashdocumentation).
- Print the total number of leaked bytes as a summary
- Added
--featuresflag. This flag is thecargo valgrindanalog to the same flag on othercargosubcommands. - deprecated
cargo_valgrind::build_target()in favor of the more flexiblecargo_valgrind::Cargotype.
- Initial release