By default, the Rake tasks for minitest and RSpec will use this configuration. When you run nfig, you are creating a default RubyMemcheck::Configuration. See the Suppression files section for more details. (Optional) If you find false positives in the output, you can create Valgrind suppression files. You're ready to run your test suite with Valgrind using rake test:valgrind or rake spec:valgrind! Note that this will take a while to run because Valgrind will make Ruby significantly slower. new ( spec: :compile ) namespace :spec do RubyMemcheck:: RSpec:: RakeTask. This is just a technical limitation that has not been solved yet (contributions welcome!). conditional jumps depending on undefined values). It will not find uses of undefined values (e.g. It will not find leaks that occur in the Init function of your native extension. To filter out false positives, it will only find definite leaks (i.e. It will not find memory leaks of allocations that occurred in Ruby (even if the memory leak is caused by your native extension).Īn example of this is if a string is allocated in Ruby, passed into your native extension, you change the pointer of the string without freeing the contents, so the contents of the string becomes leaked. So make sure your test suite has good coverage!
#VALGRIND MEMCHECK IN USE CODE#
It will only be able to report errors on code paths that are covered by your tests. This gem runs your gem's test suite to find errors and memory leaks. This gem is only expected to work on Linux. Limitationsīecause of the aggressive heuristics used to filter out false positives, there are various limitations of what this gem can detect.
It will then parse the XML and use various heuristics based on the type of the error and the stack trace to filter out errors that are false positives.įor more details, read this blog post. This gem runs Valgrind with the -xml option to generate an XML of all the errors. If your gem is written in plain Ruby, this gem is not useful for you. Only gems with native extensions can use this gem. This gem solves the problem by using heuristics to filter out false positives. This results in Valgrind reporting thousands (or more) false positives, making it very difficult for Valgrind to actually be useful.
#VALGRIND MEMCHECK IN USE FREE#
However, it doesn't work well on Ruby because Ruby does not free all of the memory it allocates during shutdown.
Valgrind's memcheck is a great tool to find and debug memory issues (e.g. This gem provides a sane way to use Valgrind's memcheck on your native extension gem.
0 kommentar(er)
