[unixODBC-support] WG: Postgresql - Freeswitch Crash

STIEG Heimo Heimo.STIEG at nextiraone.eu
Fri Oct 14 08:46:40 BST 2011


Yes, it is using the old one

        linux-vdso.so.1 =>  (0x00007fff82b5f000)
        libm.so.6 => /lib/libm.so.6 (0x00007f40ba628000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00007f40ba411000)
        libfreeswitch.so.1 => /usr/local/freeswitch/lib/libfreeswitch.so.1 (0x00                                                                                        007f40ba01a000)
        librt.so.1 => /lib/librt.so.1 (0x00007f40b9e12000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007f40b9c0e000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f40b99d6000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007f40b97ba000)
        libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00007f40b9565000)
        libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x00007f40b91c3000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x00007f40b8f7d000)
        libc.so.6 => /lib/libc.so.6 (0x00007f40b8c1c000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f40b8907000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f40b86f1000)
----->  libodbc.so.1 => /usr/lib/libodbc.so.1 (0x00007f40b848c000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f40ba8b0000)
        libltdl.so.7 => /usr/lib/libltdl.so.7 (0x00007f40b8282000)


Should I just relink /usr/lib/libodbc.so to /usr/local/lib/libodbc.so.2.0.0, or are there other things i must care of?

-----Ursprüngliche Nachricht-----
Von: unixodbc-support-bounces at mailman.unixodbc.org [mailto:unixodbc-support-bounces at mailman.unixodbc.org] Im Auftrag von Nick Gorham
Gesendet: Freitag, 14. Oktober 2011 09:27
An: Support for the unixODBC project
Betreff: Re: [unixODBC-support] WG: Postgresql - Freeswitch Crash

Ok.

 From what I can see of the log the code its failing in is calling a 
pthread_mutex_lock. in the 2.3 code that is only called if Threading is 
set. It should still not break, but if you were using the 2.3 and the 
ini is set as you have, it should not even be calling that.

Can you check that the lib built from the trubk of the code is the one 
you are now using. The trunk has changed the api number so if the ap is 
linked against libodbc.so.1 it may still be using the old one.

Check using

ldd yourapplication

to see if it shows what libodbc its using, or if its set in a ini file 
which one is loaded.

Not only because of the library number, building from source will put 
the lib in /usr/local/lib your apptitude installed one may be in 
/usr/lib so being found first.

So I think the first step is to make sure its using the unixODBC that 
you think it is.

-- 
Nick
_______________________________________________
unixODBC-support mailing list
unixODBC-support at mailman.unixodbc.org
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


More information about the unixODBC-support mailing list