From: Mike Dalessio <mike.dalessio@...>
Date: 2011-01-24T13:17:01+09:00
Subject: [ruby-core:34822] Re: MRI 1.9 valgrind errors

--90e6ba6e8a26e54618049a8fde15
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 21, 2011 at 7:29 PM, Kurt Stephens <ks@kurtstephens.com> wrote:

> I've been drilling deep into MRI's gc.
> Does anyone regularly run MRI against valgrind?
> I'm seeing quite a few errors on OS X 10.6.6 64-bit.
>
> e.g.:
>
> ==36412== Use of uninitialised value of size 8
> ==36412==    at 0x100054542: mark_current_machine_context (in ./ruby)
> ==36412==    by 0x10005473A: gc_marks (in ./ruby)
> ==36412==    by 0x1000558EA: rb_newobj (in ./ruby)
> ==36412==    by 0x100055E48: rb_node_newnode (in ./ruby)
> ==36412==    by 0x100099AA4: gettable_gen (in ./ruby)
> ==36412==    by 0x1000B752E: ruby_yyparse (in ./ruby)
> ==36412==    by 0x1000B8FC9: yycompile0 (in ./ruby)
> ==36412==    by 0x10017F7A2: thread_suppress_tracing (in ./ruby)
> ==36412==    by 0x100096E1F: rb_parser_compile_file (in ./ruby)
> ==36412==    by 0x1000FBC1B: load_file_internal (in ./ruby)
> ==36412==    by 0x10003C5CE: rb_ensure (in ./ruby)
> ==36412==    by 0x1000F950D: rb_load_file (in ./ruby)
> ==36412==
> ==36412== Conditional jump or move depends on uninitialised value(s)
> ==36412==    at 0x100051CAB: gc_mark_children (in ./ruby)
> ==36412==    by 0x100054622: mark_current_machine_context (in ./ruby)
> ==36412==    by 0x10005473A: gc_marks (in ./ruby)
> ==36412==    by 0x1000558EA: rb_newobj (in ./ruby)
> ==36412==    by 0x100055E48: rb_node_newnode (in ./ruby)
> ==36412==    by 0x100099AA4: gettable_gen (in ./ruby)
> ==36412==    by 0x1000B752E: ruby_yyparse (in ./ruby)
> ==36412==    by 0x1000B8FC9: yycompile0 (in ./ruby)
> ==36412==    by 0x10017F7A2: thread_suppress_tracing (in ./ruby)
> ==36412==    by 0x100096E1F: rb_parser_compile_file (in ./ruby)
> ==36412==    by 0x1000FBC1B: load_file_internal (in ./ruby)
> ==36412==    by 0x10003C5CE: rb_ensure (in ./ruby)
>
>
When I'm running valgrind against MRI I use

  --partial-loads-ok=yes --undef-value-errors=no

to hide these messages, which have never, in my experience, been of any use
when debugging issues with C extensions.

--90e6ba6e8a26e54618049a8fde15
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jan 21, 2011 at 7:29 PM, Kurt St=
ephens <span dir=3D"ltr">&lt;<a href=3D"mailto:ks@kurtstephens.com">ks@kurt=
stephens.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I&#39;ve been drilling deep into MRI&#39;s gc.<br>
Does anyone regularly run MRI against valgrind?<br>
I&#39;m seeing quite a few errors on OS X 10.6.6 64-bit.<br>
<br>
e.g.:<br>
<br>
=3D=3D36412=3D=3D Use of uninitialised value of size 8<br>
=3D=3D36412=3D=3D =A0 =A0at 0x100054542: mark_current_machine_context (in .=
/ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10005473A: gc_marks (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000558EA: rb_newobj (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100055E48: rb_node_newnode (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100099AA4: gettable_gen (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000B752E: ruby_yyparse (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000B8FC9: yycompile0 (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10017F7A2: thread_suppress_tracing (in ./ruby=
)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100096E1F: rb_parser_compile_file (in ./ruby)=
<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000FBC1B: load_file_internal (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10003C5CE: rb_ensure (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000F950D: rb_load_file (in ./ruby)<br>
=3D=3D36412=3D=3D<br>
=3D=3D36412=3D=3D Conditional jump or move depends on uninitialised value(s=
)<br>
=3D=3D36412=3D=3D =A0 =A0at 0x100051CAB: gc_mark_children (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100054622: mark_current_machine_context (in .=
/ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10005473A: gc_marks (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000558EA: rb_newobj (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100055E48: rb_node_newnode (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100099AA4: gettable_gen (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000B752E: ruby_yyparse (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000B8FC9: yycompile0 (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10017F7A2: thread_suppress_tracing (in ./ruby=
)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x100096E1F: rb_parser_compile_file (in ./ruby)=
<br>
=3D=3D36412=3D=3D =A0 =A0by 0x1000FBC1B: load_file_internal (in ./ruby)<br>
=3D=3D36412=3D=3D =A0 =A0by 0x10003C5CE: rb_ensure (in ./ruby)<br>
<br>
</blockquote></div><br><div>When I&#39;m running valgrind against MRI I use=
</div><div><br></div><div>=A0=A0--partial-loads-ok=3Dyes --undef-value-erro=
rs=3Dno</div><div><br></div><div>to hide these messages, which have never, =
in my experience, been of any use when debugging issues with C extensions.<=
/div>

--90e6ba6e8a26e54618049a8fde15--