Re: BUG #8093: After starting postgres, any attempt to connect generate a core dump and unable to login - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #8093: After starting postgres, any attempt to connect generate a core dump and unable to login
Date
Msg-id 15216.1366381002@sss.pgh.pa.us
Whole thread Raw
In response to BUG #8093: After starting postgres, any attempt to connect generate a core dump and unable to login  (bmohareb@gmail.com)
List pgsql-bugs
bmohareb@gmail.com writes:
> $ psql seo
> psql (9.0.4)
> Type "help" for help.

> *** glibc detected *** psql: free(): invalid next size (normal):
> 0x000000001553a9d0 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x321b871684]
> /lib64/libc.so.6(cfree+0x8c)[0x321b874ccc]
> /opt/postgres/9.0/bin/../lib/libedit.so[0x2af979babd40]
> /opt/postgres/9.0/bin/../lib/libedit.so(history+0x5a3)[0x2af979bac6da]
> /opt/postgres/9.0/bin/../lib/libedit.so(read_history+0x47)[0x2af979bbccd5]
> psql[0x40a142]
> psql[0x40fb0b]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x321b81d8b4]
> psql[0x403a69]

This looks like a bug in libedit (which I think we've heard about
before, in fact).  Try to find a newer version of libedit, or build
against GNU readline instead.

            regards, tom lane

pgsql-bugs by date:

Previous
From: catherine.devlin@gmail.com
Date:
Subject: BUG #8098: Bad option -I in contrib/start-scripts/linux
Next
From: Tom Lane
Date:
Subject: Re: BUG #8095: postgres acquiring lock on a table when not in transaction