From: Yukihiro Matsumoto <matz@...>
Date: 2012-11-06T03:59:32+09:00
Subject: Re: Ruby under Valgrind shows a ton of memory errors -- normal?

--Multipart_Tue_Nov__6_03:55:30_2012-1
Content-Type: text/plain; charset=US-ASCII

Hi,

In message "Re: Ruby under Valgrind shows a ton of memory errors -- normal?"
    on Tue, 6 Nov 2012 03:41:21 +0900, Alex Dowad <lists@ruby-forum.com> writes:

|I'm interested in whether the Ruby core team is aware of this and 
|whether it is normal. If not, I will dig deeper.

We are aware of, and this is normal.  Attached file makes warning bit
better.

							matz.


--Multipart_Tue_Nov__6_03:55:30_2012-1
Content-Type: application/octet-stream
Content-Disposition: attachment; filename=".valgrind.supp"
Content-Transfer-Encoding: quoted-printable

{
   onig_search
   Memcheck:Cond
   fun:onig_search
   fun:rb_reg_search
}
{
   is_pointer_to_heap
   Memcheck:Cond
   fun:is_pointer_to_heap
   fun:mark_locations_array
}
{
   gc_mark
   Memcheck:Value4
   fun:gc_mark
}
{
   gc_mark
   Memcheck:Cond
   fun:gc_mark
}
{
   gc_mark_children
   Memcheck:Cond
   fun:gc_mark_children
}
{
   gc_mark_children
   Memcheck:Value4
   fun:gc_mark_children
}
{
   mark_locations_array
   Memcheck:Cond
   fun:mark_locations_array
}
{
   rb_special_const_p
   Memcheck:Cond
   fun:rb_special_const_p
   fun:gc_mark
   fun:mark_locations_array
}

--Multipart_Tue_Nov__6_03:55:30_2012-1--