| Lists: | pgsql-bugs |
|---|
| From: | "Chris Vickery" <cvickery(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #3738: psql crashes on exit. |
| Date: | 2007-11-09 16:40:59 |
| Message-ID: | 200711091640.lA9GexnS065348@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 3738
Logged by: Chris Vickery
Email address: cvickery(at)gmail(dot)com
PostgreSQL version: 8.2.5
Operating system: OS X 10.4
Description: psql crashes on exit.
Details:
senate=# \q
psql(4484) malloc: *** error for object 0x1806200: incorrect checksum for
freed object - object was probably modified after being freed, break at
szone_error to debug
psql(4484) malloc: *** set a breakpoint in szone_error to debug
Segmentation fault
The problem didn't always occur, and I cannot say what caused it to start
happening. But it happens every time now. I have sometimes been running the
current version of pgAdmin3 concurrently with psql, if that's a clue.
The problem started when running 8.2.4, so I backed up the database (using
dumpall from 8.2.4), upgraded to 8.2.5, and restored the database: same
problem. The above output is from the first run of psql after the upgrade; I
have not run pgAdmin3 since the upgrade.
"szone_error" is an OS X library routine, but I'm not enough of an OS X
developer to know how to get at it.
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Chris Vickery" <cvickery(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3738: psql crashes on exit. |
| Date: | 2007-11-09 17:20:27 |
| Message-ID: | 12038.1194628827@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
"Chris Vickery" <cvickery(at)gmail(dot)com> writes:
> Description: psql crashes on exit.
We've seen this before --- there's a bug in the Apple-supplied libedit:
http://archives.postgresql.org/pgsql-hackers/2006-12/msg01222.php
My suggestion would be to rebuild using libreadline, which is a lot more
featureful anyway. If you don't want to do that, removing
~/.psql_history will make it go away (for awhile).
regards, tom lane