Roger,

Ummm... Moving binaries between different CPUs doesn't always work.
How, exactly, did the host and target machines differ?

Anyway...
The version I just pushed to github at:

http://github.com/brentr/matzruby/tree/v1_8_7_72-mbari

passed the Ruby test suite earlier this week on ppc, ppc64, arm, i386, and
x86_64 CPUs.

As mentioned in my previous post, this version should fix the failing
TestBeginEndBlock test.
Could you try building from my github repo to verify this and 
let me know if your bittorent test still fails?

I'm still new to the git stuff.  
Please let me know whether I've set up my repository correctly.

- brent


Roger Pack wrote:
> 
> 
> Here's an interesting one.
> I built 1.8.7p72 with the mbari patches.  Works fine on the computer
> where it was built.  If I run it on another computer on the same
> network, same OS [slightly different cpu], it sometimes [depending on
> the moon phase] results in:
> 
> 
> [09:1721][rdp@ilab2:~/tmp_src]$ ruby driver.rb  -pbitTorrent
> --name=yanc_and_bittorrent_100_take2
> /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems/specification.rb:48:
> [BUG] terminated node (0xb7c3505c)
> ruby 1.8.7 (2009-1-18 MBARI 7/0x4770 on patchlevel 72) [i686-linux]
> 
> Aborted
> 
> [13:2228][rdp@ilab1:~]$ gcc -v
> uReading specs from
> /home/rdp/installs/lib/gcc/i686-pc-linux-gnu/3.4.6/specs
> Configured with: ./configure --prefix=/home/rdp/installs
> Thread model: posix
> gcc version 3.4.6
> [13:2228][rdp@ilab1:~]$ uname -a
> Linux ilab1 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686
> GNU/Linux
> 
> make test-all clears except a few zlib errors [it isn't installed] and
> 
>   4) Failure:
> test_should_propagate_signaled(TestBeginEndBlock)
> [./test/ruby/test_beginendblock.rb:81]:
> <""> expected to be =~
> </Interrupt$/>.
> 
> any thoughts?
> Thanks!
> -=r
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p22010810.html
Sent from the ruby-core mailing list archive at Nabble.com.