Re: Postgresql 9.0.1 installation error

Below is the output of "ldd" and "gdb output with 'bt argument' "

ldd output
========

[postgres(at)warehouse1 bin]$ ldd ./psql
libpq.so.5 => /opt/Postgres9.0.1/lib/libpq.so.5 (0x00002b354bb1a000)
libedit.so.0 => /usr/lib64/libedit.so.0 (0x00002b354bd49000)
libc.so.6 => /lib64/libc.so.6 (0x0000003c52e00000)
libldap_r-2.3.so.0 => /usr/lib64/libldap_r-2.3.so.0
(0x00002b354bf77000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003c53a00000)
libncurses.so.5 => /usr/lib64/libncurses.so.5 (0x0000003c55e00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003c52a00000)
liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x0000003c56a00000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003c56200000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x0000003c55200000)
libssl.so.6 => /lib64/libssl.so.6 (0x00000038a0600000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x000000389f200000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003c53200000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003c55600000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
(0x000000389fa00000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x000000389f600000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003c56600000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000038a0200000)
libz.so.1 => /usr/lib64/libz.so.1 (0x0000003c53e00000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
(0x000000389fe00000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003c59a00000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x000000389ee00000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003c54a00000)

gdb output with "bt"
===============

[postgres(at)warehouse1 bin]$ gdb --args ./psql -p 6444
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5_5.2)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /opt/Postgres9.0.1/bin/psql...done.
(gdb) run
Starting program: /opt/Postgres9.0.1/bin/psql -p 6444
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00002aaaaaac3b8c in resetPQExpBuffer () from
/opt/Postgres9.0.1/lib/libpq.so.5
(gdb) bt
#0 0x00002aaaaaac3b8c in resetPQExpBuffer () from
/opt/Postgres9.0.1/lib/libpq.so.5
#1 0x00002aaaaaabd610 in pqGets_internal () from
/opt/Postgres9.0.1/lib/libpq.so.5
#2 0x0000000000658d70 in ?? ()
#3 0x0000000000658d70 in ?? ()
#4 0x0000000000659188 in ?? ()
#5 0x0000000000000000 in ?? ()

Thanks,
Nag

On Wed, Aug 10, 2011 at 11:42 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>wrote:

> On 9/08/2011 2:31 PM, Venkat Balaji wrote:
>
>> Hi Craig,
>>
>> Thank you very much for your reply !
>>
>> Here is my reply -
>>
>> 1. We are using RHEL with the below version
>> Linux version 2.6.18-194.26.1.el5
>> (mockbuild(at)x86-004(dot)build(dot)bos(dot)**redhat(dot)com<mockbuild(at)x86-004(dot)build(dot)bos(dot)redhat(dot)com>
>> <mailto:mockbuild(at)x86-004(dot)**build(dot)bos(dot)redhat(dot)com<mockbuild(at)x86-004(dot)build(dot)bos(dot)redhat(dot)com>>)
>> (gcc version 4.1.2
>>
>> 20080704 (Red Hat 4.1.2-48)) #1 SMP Fri Oct 29 14:21:16 EDT 2010
>>
>> 2. LD_LIBRARY_PATH is not set
>>
>
> OK. In that case, please show the output of:
>
> ldd ./psql
>
> run in exactly the same environment as you'd run ./psql and get a crash.
>
>
>
>
> Program received signal SIGSEGV, Segmentation fault.
>> 0x00002aaaaaac2ecc in resetPQExpBuffer () from
>> /opt/Postgres9.0.1/lib/libpq.**so.5
>>
>
> OK, you haven't built with debugging. Try rebuilding with --enable-debug to
> configure, then re-running the gdb command. When you get a crash and the
> above message is printed out, you'll get a prompt like:
>
> (gdb)
>
> Type "bt" at that prompt and press enter. The resulting stack trace shows
> more information about what led up to the crash.
>
> Debugging memory related crashes in C isn't simple. Just because it crashes
> in libpq doesn't mean the fault is in libpq. It might be, or it might be
> that some other library is corrupting memory that causes libpq to crash
> later, corrupting the stack, returning a bad pointer from a function call,
> library headers not matching linked library sizes so returned struct
> sizes/offsets are wrong, and lots lots more. It's not simple.
>
> --
> Craig Ringer
>