devel/rubygem-ruby_memcheck: Update to 3.0.1 Changes: https://github.com/Shopify/ruby_memcheck/releasesb151c84e1f
Port details
devel/rubygem-ruby_memcheck 3.0.1
Use Valgrind memcheck without going crazy
- Maintainer
- sunpoet@FreeBSD.org
- Packages
- latest: 3.0.1
- Upstream
- up to date
- Last update
- to 3.0.1 · b151c84e1f
- Quarterly
- 2026Q4: 3.0.1
- WWW
- https://github.com/Shopify/ruby_memcheck
- Links
- cgit · VuXML
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 3.0.1.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (7)
devel/rubygem-ruby_memcheck: Update to 3.0.0 Changes: https://github.com/Shopify/ruby_memcheck/releasesfde8470f61
devel/rubygem-ruby_memcheck: Update to 2.3.0 Changes: https://github.com/Shopify/ruby_memcheck/releasesdc2c2973ba
devel/rubygem-ruby_memcheck: Update to 2.2.1 Changes: https://github.com/Shopify/ruby_memcheck/releasesc6dec7bbaa
devel/rubygem-ruby_memcheck: Update to 2.2.0 Changes: https://github.com/Shopify/ruby_memcheck/releases5f9aaefbb3
devel/rubygem-ruby_memcheck: Update to 2.1.2 Changes: https://github.com/Shopify/ruby_memcheck/releasesf06ce42bb7
devel/rubygem-ruby_memcheck: Add rubygem-ruby_memcheck 2.1.1 ruby_memcheck provides a sane way to use Valgrind's memcheck on your native extension gem. Valgrind's memcheck is a great tool to find and debug memory issues (e.g. memory leak, use-after-free, etc.). However, it doesn't work well on Ruby because Ruby does not free all of the memory it allocates during shutdown. This results in Valgrind reporting thousands (or more) false positives, making it very difficult for Valgrind to actually be useful. This gem solves the problem by using heuristics to filter out false positives.c5a3c98e4a