From: Brent Roman <brent@...>
Date: 2009-01-15T03:26:26+09:00
Subject: [ruby-core:21348] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use


Oh... Never mind :-)

If you are running Intel OSx, you've basically got a tweaked, slightly
outdated
Apple fork of GNU gcc for i386.  Others have reported on and off problems
compiling ruby with -O3 and/or -fomit-frame-pointer.  I was pleasantly
surprised
when I discovered that -fomit-frame-pointer no longer crashes ruby with
gcc 4.3.2.  But, I would never recommend it on the i386 as a default for
building
ruby.  I've also noticed that i386 -O3 produces a Ruby interpreter that
benchmarks
slower than one compiled with -O2.  You might want to confirm this for
yourself.

See my comments below:

Stephen Sykes-3 wrote:
> 
> 
> Last evening I ran into the following issue with my recently compiled
> ruby (which I had compiled with the -O3 options I gave before):
> 
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:333: [BUG] Bus
> Error
> ruby 1.8.7 (2009-1-11 MBARI 7/0x4370 on patchlevel 72) [i686-darwin9.6.0]
> Abort trap
> 
> I recomplied with your suggested options of
> -O2 -fno-stack-protector
> and this problem went away.  Perhaps best to stick with these options for
> now.
> 
> 

You had mentioned setting STACK_WIPE_SITES to 0x4370.
Do you also get this error with STACK_WIPE_SITES left at its default of
0x2370 ?

I would be willing to try debugging the problem on my Mac Mini after
rebooting it into OSx,
if this failure occurs with the default STACK_WIPE_SITES 0x2*** settings
using gcc options
that otherwise yield a stable unpatched ruby build,

- brent


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