--000e0cd6a9408ec0bf0463348912
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I will try and take a look at this soon, hopefully before the end of the
week...

- Michael

On Tue, Feb 17, 2009 at 2:18 PM, Brent Roman <brent / mbari.org> wrote:

>
> I just pushed out a version of the MBARI patches for Ruby 1.8.6-p287 onto:
>
> git://github.com/brentr/matzruby.git
>
> in the branch v1_8_6_287-mbari
>
> I'm down to just one test failure:
>
>  1) Error:
> test_object_id_collision(YAML_Unit_Tests):
> RuntimeError: id collision in ordered map
>    ./test/yaml/test_yaml.rb:1281:in `test_object_id_collision'
>
> However, I'm not motivated to investigate much further because this
> test fails on every version of 1.8.6-p287 I build from source on
> four different linux boxes with varying versions of gcc including those
> built directly from the archive:
>
> ftp://ruby-lang.org/pub/ruby/ruby-1.8.6-p287.tar.bz2
>
> On the other hand, I recall Michael King claimed to have gotten 1.8.6-p287
> to complete
> the test suite without any errors whatsoever.
>
> I'm building like this:
> $  CFLAGSO2 -fno-stack-protector" configure --prefixOME/ruby/test
> $ make -j3 && make install
>
> (I've tried all sorts of CFLAGS, so please no comments about those)
> and running the yaml test with:
>
> $  cd test
> $  ~/ruby/test/bin/ruby  runner.rb  yaml
> Loaded suite yaml
> Started
> .........E................................................
> Finished in 0.409985 seconds.
>
>  1) Error:
> test_object_id_collision(YAML_Unit_Tests):
> RuntimeError: id collision in ordered map
>   ./yaml/test_yaml.rb:1281:in `test_object_id_collision'
>
> 58 tests, 206 assertions, 0 failures, 1 errors
>
> If you try that on your Ruby 1.8.6-p287 built from source,
> do you see the error?
>
> Is there another way to build it from source that avoids the error?
>
> Please respond with details on your build procedure, environment etc.
> only if you've built Ruby 1.8.6-p287 from source and do not see the above
> error.
> If you've got it working, I'd sure like to how exactly how!
>
> - brent
>
> P.S.  Note that this issue was supposedly fixed by a patch applied on
> 6/15/08.
> That patch appears to be present in 1.8.6-p287.
> See http://redmine.ruby-lang.org/issues/show/411
> If no one responds, I'll add this report to redmine, but for now, I'm
> assuming
> I've got a problem with my build procedure.
>
> --
> View this message in context:
> http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p22065464.html
> Sent from the ruby-core mailing list archive at Nabble.com.
>
>
>

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

I will try and take a look at this soon, hopefully before the end of the week...<br><br>- Michael <br><br><div class="gmail_quote">On Tue, Feb 17, 2009 at 2:18 PM, Brent Roman <span dir="ltr">&lt;brent / mbari.org&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I just pushed out a version of the MBARI patches for Ruby 1.8.6-p287 onto:<br>
<br>
git://<a href="http://github.com/brentr/matzruby.git" target="_blank">github.com/brentr/matzruby.git</a><br>
<br>
in the branch v1_8_6_287-mbari<br>
<br>
I&#39;m down to just one test failure:<br>
<br>
 &nbsp;1) Error:<br>
test_object_id_collision(YAML_Unit_Tests):<br>
RuntimeError: id collision in ordered map<br>
 &nbsp; &nbsp;./test/yaml/test_yaml.rb:1281:in `test_object_id_collision&#39;<br>
<br>
However, I&#39;m not motivated to investigate much further because this<br>
test fails on every version of 1.8.6-p287 I build from source on<br>
four different linux boxes with varying versions of gcc including those<br>
built directly from the archive:<br>
<br>
<a href="ftp://ruby-lang.org/pub/ruby/ruby-1.8.6-p287.tar.bz2" target="_blank">ftp://ruby-lang.org/pub/ruby/ruby-1.8.6-p287.tar.bz2</a><br>
<br>
On the other hand, I recall Michael King claimed to have gotten 1.8.6-p287<br>
to complete<br>
the test suite without any errors whatsoever.<br>
<br>
I&#39;m building like this:<br>
$ &nbsp;CFLAGS=&quot;-O2 -fno-stack-protector&quot; configure --prefix=$HOME/ruby/test<br>
$ make -j3 &amp;&amp; make install<br>
<br>
(I&#39;ve tried all sorts of CFLAGS, so please no comments about those)<br>
and running the yaml test with:<br>
<br>
$ &nbsp;cd test<br>
$ &nbsp;~/ruby/test/bin/ruby &nbsp;runner.rb &nbsp;yaml<br>
Loaded suite yaml<br>
Started<br>
.........E................................................<br>
Finished in 0.409985 seconds.<br>
<br>
&nbsp;1) Error:<br>
test_object_id_collision(YAML_Unit_Tests):<br>
RuntimeError: id collision in ordered map<br>
 &nbsp; ./yaml/test_yaml.rb:1281:in `test_object_id_collision&#39;<br>
<br>
58 tests, 206 assertions, 0 failures, 1 errors<br>
<br>
If you try that on your Ruby 1.8.6-p287 built from source,<br>
do you see the error?<br>
<br>
Is there another way to build it from source that avoids the error?<br>
<br>
Please respond with details on your build procedure, environment etc.<br>
only if you&#39;ve built Ruby 1.8.6-p287 from source and do not see the above<br>
error.<br>
If you&#39;ve got it working, I&#39;d sure like to how exactly how!<br>
<br>
- brent<br>
<br>
P.S. &nbsp;Note that this issue was supposedly fixed by a patch applied on<br>
6/15/08.<br>
That patch appears to be present in 1.8.6-p287.<br>
See <a href="http://redmine.ruby-lang.org/issues/show/411" target="_blank">http://redmine.ruby-lang.org/issues/show/411</a><br>
If no one responds, I&#39;ll add this report to redmine, but for now, I&#39;m<br>
assuming<br>
I&#39;ve got a problem with my build procedure.<br>
<font color="#888888"><br>
--<br>
View this message in context: <a href="http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p22065464.html" target="_blank">http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p22065464.html</a><br>

Sent from the ruby-core mailing list archive at Nabble.com.<br>
<br>
<br>
</font></blockquote></div><br>

--000e0cd6a9408ec0bf0463348912--