v2.1.0 (test only)

This tests the new deployment strategy implemented in #75, thanks @Luni-4.

Version 2.1.0

• Support passing additional flags to valgrind via the VALGRINDFLAGS env var (thanks @Avuxo, @ki7dk)
• Deploy releases automatically, including build artifacts (thanks @Luni-4)
• Accept more Valgrind XML output (leading to fewer panics) (thanks @TheWastl)
• Update dependencies including a fix for a vulnerability in regex (which didn't affect this crate, though)
• Fix typos (thanks @wiktor-k, @krystian-wojtas)

Version 2.0.3

Changelog

• Update dependencies

Version 2.0.2

Changelog

• Support absence of xwhat in valgrind XML output (#49, thanks to @vhqtvn)

Version 2.0.1

Changelog

• 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

Version 2.0.0

Breaking change

This release marks a complete rework of the cargo-valgrind tool in version 1.x. This includes two kinds of change:

1. CLI changes, that directly influence the users
2. internal code changes in this tool

CLI changes

The first change is the most important one: instead of handling everything by cargo valgrind <FLAGS>, where <FLAGS> denote the actual action, the program is now called like this:

• cargo valgrind run for running the current binary
• cargo valgrind test for running all kinds of tests
• cargo valgrind run --example foo for running the example foo
• ...

This new command line supports every runnable target, that the normal cargo supports (likely even other cargo subcommands). Therefore most user-issues like "unit tests cannot be run" are now a thing of the past!
The downside of this change is the new command line, that has to be used. The changed command line is necessary due to the following internal changes:

Internal changes

This release marks a step in a completely new direction of this tool. Instead of parsing the command line and crucially the cargo metadata ourselves, the tool now uses cargo itself to handle the stuff, cargo knows about the best: what binary is produced by which command (the building was done by cargo in the older version 1.x of cargo-valgrind).
This greatly reduces the lines of code needed, as well as the complexity of the code. The now much more simple code is therefore also extendible in a more easy way.

Version 1.3.0

Changelog

• Support user flags for the analyzed binary.

Version 1.2.3

Changelog

• Updated dependencies

Version 1.2.2

Changelog

• 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

Version 1.2.1

Changelog

• 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