From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5589: psql dies with bad free() in libedit |
Date: | 2010-08-02 05:19:42 |
Message-ID: | 08A79DC4-DD62-44F5-A99F-1F732AB084FC@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Aug 1, 2010, at 10:11 PM, Tom Lane wrote:
> "Steve Atkins" <steve(at)blighty(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | John Regehr | 2010-08-02 06:07:21 | BUG #5590: undefined shift behavior |
Previous Message | Tom Lane | 2010-08-02 05:11:49 | Re: BUG #5589: psql dies with bad free() in libedit |