Re: Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1
Date
Msg-id 949.989934736@sss.pgh.pa.us
Whole thread Raw
In response to Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1  (Paul McGarry <PaulM@opentec.com.au>)
List pgsql-bugs
Paul McGarry <PaulM@opentec.com.au> writes:
> Program received signal SIGSEGV, Segmentation fault.
> 0xff363b60 in __do_global_dtors_aux () from /opt/pgsql/lib/libpq.so.2
> (gdb) bt
> #0  0xff363b60 in __do_global_dtors_aux () from /opt/pgsql/lib/libpq.so.2
> #1  0xff3728d4 in _fini () from /opt/pgsql/lib/libpq.so.2
> #2  0xff3ba060 in ?? ()
> #3  0xff0a0130 in _exithandle () from /usr/lib/libc.so.1
> #4  0xff116964 in exit () from /usr/lib/libc.so.1

This appears to be psql dying, not the backend.  Renaud Thonnart
<thonnart@amwdb.u-strasbg.fr> reported a similar problem on his Solaris
setup last week (4-May in pgsql-general), but so far as I heard no one
had a clue what the problem was.  <WAG> Shared library linkage problem,
maybe? </WAG>

            regards, tom lane

pgsql-bugs by date:

Previous
From: Paul McGarry
Date:
Subject: RE: Segfault in pgsql, Sparc Solaris 2.7, Postgresql 7.1.1
Next
From: Chris Storah
Date:
Subject: socket slowdown using libpg and 7.1.1 ?