Date: Mon, 21 Aug 2023 17:13:02 GMT From: Po-Chuan Hsieh <sunpoet@FreeBSD.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: git: c5a3c98e4acb - main - devel/rubygem-ruby_memcheck: Add rubygem-ruby_memcheck 2.1.1 Message-ID: <202308211713.37LHD2On097597@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by sunpoet: URL: https://cgit.FreeBSD.org/ports/commit/?id=c5a3c98e4acbbda628a775a09f8768fe2f2e0b86 commit c5a3c98e4acbbda628a775a09f8768fe2f2e0b86 Author: Po-Chuan Hsieh <sunpoet@FreeBSD.org> AuthorDate: 2023-08-21 16:52:03 +0000 Commit: Po-Chuan Hsieh <sunpoet@FreeBSD.org> CommitDate: 2023-08-21 17:01:59 +0000 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. --- devel/Makefile | 1 + devel/rubygem-ruby_memcheck/Makefile | 22 ++++++++++++++++++++++ devel/rubygem-ruby_memcheck/distinfo | 3 +++ devel/rubygem-ruby_memcheck/pkg-descr | 9 +++++++++ 4 files changed, 35 insertions(+) diff --git a/devel/Makefile b/devel/Makefile index 10d1f5b0fa14..30eff0fa80a5 100644 --- a/devel/Makefile +++ b/devel/Makefile @@ -7281,6 +7281,7 @@ SUBDIR += rubygem-ruby2_keywords SUBDIR += rubygem-ruby2ruby SUBDIR += rubygem-ruby_dep + SUBDIR += rubygem-ruby_memcheck SUBDIR += rubygem-ruby_parser SUBDIR += rubygem-rubygems-mirror SUBDIR += rubygem-rubygems-tasks diff --git a/devel/rubygem-ruby_memcheck/Makefile b/devel/rubygem-ruby_memcheck/Makefile new file mode 100644 index 000000000000..1168216a82e2 --- /dev/null +++ b/devel/rubygem-ruby_memcheck/Makefile @@ -0,0 +1,22 @@ +PORTNAME= ruby_memcheck +PORTVERSION= 2.1.1 +CATEGORIES= devel rubygems +MASTER_SITES= RG + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Use Valgrind memcheck without going crazy +WWW= https://github.com/Shopify/ruby_memcheck + +LICENSE= MIT +LICENSE_FILE= ${WRKSRC}/LICENSE.txt + +RUN_DEPENDS= rubygem-nokogiri>=0:textproc/rubygem-nokogiri \ + valgrind>=3.20.0,1:devel/valgrind + +USES= gem + +NO_ARCH= yes + +PLIST_FILES= bin/ruby_memcheck + +.include <bsd.port.mk> diff --git a/devel/rubygem-ruby_memcheck/distinfo b/devel/rubygem-ruby_memcheck/distinfo new file mode 100644 index 000000000000..eb94e822d713 --- /dev/null +++ b/devel/rubygem-ruby_memcheck/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1692211625 +SHA256 (rubygem/ruby_memcheck-2.1.1.gem) = 83ddcbdd2517f096d632969969d12827915921624aa57d936be200d0bc18ed45 +SIZE (rubygem/ruby_memcheck-2.1.1.gem) = 15360 diff --git a/devel/rubygem-ruby_memcheck/pkg-descr b/devel/rubygem-ruby_memcheck/pkg-descr new file mode 100644 index 000000000000..73a2e30b740e --- /dev/null +++ b/devel/rubygem-ruby_memcheck/pkg-descr @@ -0,0 +1,9 @@ +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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202308211713.37LHD2On097597>