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

On Sat, May 01, 2004 at 12:13:22AM +0900, Dick Davies wrote:
> This is probably a platform thing, I'm using cvs ruby
> on NetBSD 1.6Z ...
> 
> I can use most ruby libs ok, but there's a coredump whenever
> I try to use a shared library
> (seen it so far in ruby-ldap and ruby-postgresql)

Actually, I had also some ruby coredumps while developing an
extension on Linux. Apparently, it was my fault; while I was
tweaking my code, it seems that a simple 'make' resulted to
a broken shared lib. 

This happened quite a few times. The solution was to do a 
'make clean' and then rebuild my extension.

Apart from the above, what I wanted to say here is: should ruby 
coredump?

I think it should not for any reason. 

I may be bogus on that, but I believe there must be some way
to abort on dlopen() when something seems to go wrong. ANW, I
can offer my help and my time to fix the problem if it is 
something that can be achieved.

Last but not least, I tried to reproduce the coredump with no
avail.

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