From: Elias Athanasopoulos <elathan@...>
Date: 2004-05-01T07:47:00+09:00
Subject: Re: ruby CVS can't use shared libs on NetBSD

On Sat, May 01, 2004 at 05:32:39AM +0900, Dick Davies wrote:
> * Elias Athanasopoulos <elathan@phys.uoa.gr> [0436 18:36]:
> > 
> > Apart from the above, what I wanted to say here is: should ruby 
> > coredump?
> > 
> > I think it should not for any reason. 
> 
> Not ideally, but it's a CVS build - and it's a C library issue
> at the end of the day.

In my case it was ruby 1.8/1.8.1. Even if it's the case of an 
extension Ruby, IMHO, should never core dump. The core is produced 
in the Ruby load code; not inside the extension.

> > I may be bogus on that, but I believe there must be some way
> > to abort on dlopen() when something seems to go wrong.
> 
> But if it didn't dump core. how would you find out why it failed?

The core was dumped because Ruby had received a SEGV and not the
code inside in the extension. I.e., you could force Ruby to 
segfault by:

% ruby -rfoo -e ''

Regards,
-- 
University of Athens			I bet the human brain 
Physics Department				is a kludge --Marvin Minsky