From: Blake Miller <blakeage@...>
Date: 2007-02-20T07:19:10+09:00
Subject: Re: Bus errors & segfaults

Edwin Fine wrote:
> * Has this been happening right from the start?
> * When did you first notice this behavior?
> * Do you have any Ruby extensions that might have been compiled with 
> different compiler flags to the ones used to compile Ruby?

I believe the problem is actually due to the openbase bindings that we 
are using for our Rails application.  I've talked to the developer, and, 
while the errors do not all occur in the openbase bindings/adapter, he 
feels that the bindings 0.7.3 are actually corrupting Ruby's memory, and 
causing errors elsewhere.

These errors have been around since the beginning of development of our 
ROR application, but seemed to subside when putting the app in 
production.  New to our setup was Mongrel as our application server, 
which crashes whenever malloc throws an error like above.  Webrick seems 
to handle them without crashing (for the past couple hours anyway).  So, 
for now, we're running Webrick instead of Mongrel.

So, I apologize for posting to the Ruby list, it just seemed general 
enough to be a Ruby error (and since one of the errors did not seem 
Rails-related).

The developer is working hard on the next version of the OpenBase 
bindings, so we should have a solution in a couple days.

Thanks for the lengthy input.

-- 
Posted via http://www.ruby-forum.com/.