Re: BUG #5589: psql dies with bad free() in libedit - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5589: psql dies with bad free() in libedit
Date
Msg-id 25152.1280725909@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5589: psql dies with bad free() in libedit  ("Steve Atkins" <steve@blighty.com>)
Responses Re: BUG #5589: psql dies with bad free() in libedit
List pgsql-bugs
"Steve Atkins" <steve@blighty.com> writes:
> I have a database that contains two tables (partminer and partminer2), and
> two sequences (partminer2_id_seq and partminer_pk), on a 9.0beta3
> installation built from source with default configure options.
> From psql, entering "\d p<tab>" works as expected. Entering "\d pa<tab>"
> throws an abort from malloc(): "malloc: *** error for object 0x3: pointer
> being freed was not allocated", with the error within libedit.

This sounds a lot like a known bug in Apple's version of libedit:
http://archives.postgresql.org/pgsql-bugs/2010-04/msg00127.php

libedit has proven pretty buggy over the years, and Apple isn't too
speedy to fix it.  The best bet really is to use GNU readline instead.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Steve Atkins"
Date:
Subject: BUG #5589: psql dies with bad free() in libedit
Next
From: Steve Atkins
Date:
Subject: Re: BUG #5589: psql dies with bad free() in libedit