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

From Steve Atkins
Subject Re: BUG #5589: psql dies with bad free() in libedit
Date
Msg-id 08A79DC4-DD62-44F5-A99F-1F732AB084FC@blighty.com
Whole thread Raw
In response to Re: BUG #5589: psql dies with bad free() in libedit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Aug 1, 2010, at 10:11 PM, Tom Lane wrote:

> "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

Ew. Yes it does.

> 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.

Yup.

Cheers,
  Steve

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5589: psql dies with bad free() in libedit
Next
From: Kenichiro Tanaka
Date:
Subject: Re: failed to fetch tuple for EvalPlanQual recheck