| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joseph Tate <jtate+pgsql(at)dragonstrider(dot)com> |
| Cc: | PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Seg Fault when using modules linked both to libpq and libodbcpsql. |
| Date: | 2003-12-03 16:52:55 |
| Message-ID: | 1224.1070470375@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Joseph Tate <jtate+pgsql(at)dragonstrider(dot)com> writes:
> (gdb) where
> #0 0xb69f7987 in CC_send_function () from /usr/lib/libodbcpsql.so.2
> #1 0xb6a06940 in lo_creat () from /usr/lib/libodbcpsql.so.2
> #2 0xb69c6c23 in lo_import () from /usr/lib/libpq.so.3
> #3 0xb69e4121 in zif_pg_lo_import (ht=2, return_value=0x8307424,
> this_ptr=0x0, return_value_used=1)
> at /usr/src/debug/php-4.3.2/ext/pgsql/pgsql.c:2099
> I don't know why libpq is calling into the libodbcpsql library.
It's not supposed to do that.
> It appears that somehow that libodbcpsql stuff is interfering with
> libpq. Are there some symbols that could be clobbering each other?
Looks like a conflict on "lo_creat", to start with ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvar Freude | 2003-12-03 17:20:48 | bytea, index and like operator |
| Previous Message | Olaf Hartmann | 2003-12-03 16:49:41 | libpq3 + ssl memory leak |