Skip to content

Latest commit

 

History

History
80 lines (63 loc) · 3.29 KB

CHANGELOG.md

File metadata and controls

80 lines (63 loc) · 3.29 KB

Changelog

unreleased

  • Add more helpful error message if the program under test overflows its stack (#93)
  • Perform LTO on release (#109)
  • Updated documentation
  • Raised MSRV to 1.58

Version 2.2.1

  • Ensure, that consistent tag names are used (#89). This will cause future releases to automatically include the pre-built artifacts thanks to running the deploy workflow when a new tag is pushed.

Version 2.2.0

  • Don't crash on valgrind output with multiple stack traces (e.g. an invalid read as in #80)
  • Display auxiliary information and stack traces if available (#81)
  • Update dependencies and CI configuration to fix vulnerabilities (atty and actions/checkout)

Version 2.1.0

  • Support passing additional flags to valgrind via the VALGRINDFLAGS env 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)

Version 2.0.3

  • rework continuos integration tests and automate release workflow
  • Update dependencies

Version 2.0.2

  • Support absence of xwhat in valgrind XML output

Version 2.0.1

  • 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 API and CLI change!

  • Support running every cargo executable (binary, unit tests, doctests, ...)
  • changed command line
    • cargo valgrind -> cargo valgrind run
    • cargo valgrind --tests -> cargo valgrind test
    • cargo valgrind --example asdf -> cargo valgrind run --example asdf
    • etc.
  • currently no valgrind parameter support

Version 1.3.0

  • Support user flags for the analyzed binary.

Version 1.2.3

  • Updated dependencies

Version 1.2.2

  • 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

  • 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

Version 1.2.0

  • Support the valgrind parameter --show-leak-kinds=<set>
  • Support the valgrind parameter --leak-check=<summary|full>

Version 1.1.2

  • Manually implement Hash for Target. This was previously derived, which was wrong due to the custom PartialEq-implementation (refer to the Hash documentation).

Version 1.1.1

  • Print the total number of leaked bytes as a summary

Version 1.1.0

  • Added --features flag. This flag is the cargo valgrind analog to the same flag on other cargo subcommands.
  • deprecated cargo_valgrind::build_target() in favor of the more flexible cargo_valgrind::Cargo type.

Version 1.0.0

  • Initial release