Skip to content

Fix spec:valgrind task by adopting ruby_memcheck#90

Merged
Watson1978 merged 3 commits intosocketry:mainfrom
Watson1978:ruby_memcheck
Mar 21, 2026
Merged

Fix spec:valgrind task by adopting ruby_memcheck#90
Watson1978 merged 3 commits intosocketry:mainfrom
Watson1978:ruby_memcheck

Conversation

@Watson1978
Copy link
Copy Markdown
Collaborator

@Watson1978 Watson1978 commented Mar 18, 2026

The existing spec:valgrind task fails with the following error on modern environments: NameError: uninitialized constant RUBY

Instead of just fixing the outdated constant, this commit replaces the old custom Valgrind command builder with the ruby_memcheck gem. This modernizes the memory check process and automatically handles Valgrind suppressions for Ruby's internal memory allocations, making it much easier to detect actual memory leaks in the C extension.

Types of Changes

  • Maintenance.

Contribution

@Watson1978 Watson1978 force-pushed the ruby_memcheck branch 3 times, most recently from 8a63490 to 4ca1038 Compare March 18, 2026 01:52
The existing `spec:valgrind` task fails with the following error on modern environments:
`NameError: uninitialized constant RUBY`

Instead of just fixing the outdated constant, this commit replaces the old custom Valgrind command builder with the `ruby_memcheck` gem.
This modernizes the memory check process and automatically handles Valgrind suppressions for Ruby's internal memory allocations, making it much easier to detect actual memory leaks in the C extension.
@Watson1978 Watson1978 merged commit 1a07a80 into socketry:main Mar 21, 2026
12 of 14 checks passed
@Watson1978 Watson1978 deleted the ruby_memcheck branch March 21, 2026 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant