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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bmohareb(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8093: After starting postgres, any attempt to connect generate a core dump and unable to login
Date: 2013-04-19 14:16:42
Message-ID: 15216.1366381002@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

bmohareb(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-04-19 16:52:10 Re: BUG #8095: postgres acquiring lock on a table when not in transaction
Previous Message catherine.devlin 2013-04-19 12:09:21 BUG #8098: Bad option -I in contrib/start-scripts/linux