| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Steve Atkins" <steve(at)blighty(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5589: psql dies with bad free() in libedit |
| Date: | 2010-08-02 05:11:49 |
| Message-ID: | 25152.1280725909@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"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
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2010-08-02 05:19:42 | Re: BUG #5589: psql dies with bad free() in libedit |
| Previous Message | Steve Atkins | 2010-08-02 04:19:22 | BUG #5589: psql dies with bad free() in libedit |