Thread: psql client segfault

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi, me again :-)


ok, after installing the rpm's everything was fine except connecting to
the database using the supplied client program psql. It ended with a
segmentation fault. So I thought it would be a good idea to try to install
the software from source.

The problem is, psql still exists with a segfault :-(
After the segfault the terminal became unusable, that's why I think it
could have to something with curses ...?

My setup:

RedHat 5.2 (yes)
glibc 2.1.2-11
Kernel 2.2.12-20
ncurses 4.2-10
termcap 9.12.6-15
readline 2.2.1-1

I get the segfault both as postgres user or as any other user (including
root). createdb/createuser works well, compilation of the sources too, no
errors or warnings (well, some really unimportant unused defs...).

I don't want to bother everybody on this list with huge attachments, so I
put the coredump as well as the strace output on my webpage:

http://www.0x49.org/~scip/psql-7.0.2-segfault.strace.tar.gz.

Thanks in advance,
    Thomas



- --
=> PGP key: http://daemon.de/key.txt
=> "Experience is what you got  when
=>  you did not get what you wanted."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6Afvqi8dcrd1c6OsRAiZXAKDvGp96fgctrY4Ec9x0QEujT4iTCgCgt1Qd
CJFZlBWMTRdF2s7KBqMoJWk=
=ZaSj
-----END PGP SIGNATURE-----

A corefile is of no value to anyone running on a platform even slightly
different from your own.  Could you please compile psql with -g,
reproduce the problem, and then send in a gdb backtrace from that core?

Also, what exactly are you doing that provokes the coredump?

FWIW, I have a RedHat 5.1 box on which I sometimes test postgres,
so the mere fact that your system is old isn't the issue.

            regards, tom lane