You can fix it for yourself by removing the RTLD_GROUP from unixODBC and rebuilding it. See the FAQ I pointed you at.
Martin -- Martin J. Evans Easysoft Ltd, UK Development On 19-May-2005 Stephen More wrote: >> The interesting thing is I can't see unixODBC - I thought you were using >> unixODBC? > > I think I am using it. ldd shows ODBC.so is linked to it: > > $ ldd > /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/auto/DBD/ODBC/ODBC.so > libodbc.so.1 => /usr/lib/libodbc.so.1 (0x00be6000) > libc.so.6 => /lib/tls/libc.so.6 (0x00111000) > libltdl.so.3 => /usr/lib/libltdl.so.3 (0x00f62000) > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x0023a000) > /lib/ld-linux.so.2 (0x008f6000) > libdl.so.2 => /lib/libdl.so.2 (0x00eff000) > $ rpm --query -f /usr/lib/libodbc.so.1 > unixODBC-2.2.9-1 > $ > > >> You need to try PERL_DL_NONLAZY=1. If the problem goes away then see the >> rest >> of the faq above for how to make sure unixODBC is built without the >> RTLD_GROUP >> flag to dlopen. > > $ PERL_DL_NONLAZY=1 > $ export PERL_DL_NONLAZY > > That seems to have gotten rid of the Seg Fault ! > > I'll try to open up a bug with RedHat so this can be fixed in the > distribution. > > Thanks for all your help. > -Steve More
