BUG #1959: readline error exiting psql

Started by David E. Wheelerover 20 years ago3 messagesbugs
Jump to latest
#1David E. Wheeler
david@kineticode.com

The following bug has been logged online:

Bug reference: 1959
Logged by: David Wheeler
Email address: david@kineticode.com
PostgreSQL version: 8.1b3
Operating system: Mac OS X 10.4 "Tiger"
Description: readline error exiting psql
Details:

At least it doesn't segfault anymore, but when exiting psql with 8.1b3 on
Mac OS X 10.4 "Tiger" with Apple's wacko readline library, I get the
following error:

could not save history to file "/Users/david/.psql_history": Invalid
argument

Hrm. No, I just went in and ran a query, then quit, and then it said:

psql(14102) malloc: *** error for object 0x1807000: incorrect checksum for
freed object - object was probably modified after being freed, break at
szone_error to debug
psql(14102) malloc: *** set a breakpoint in szone_error to debug
zsh: segmentation fault /usr/local/pgsql/bin/psql -U postgres -d sharky

Bummer. The weird thing is that the query I ran does show up in the history
if I go into psql again. Very odd.

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: David E. Wheeler (#1)
Re: BUG #1959: readline error exiting psql

"David Wheeler" <david@kineticode.com> writes:

Hrm. No, I just went in and ran a query, then quit, and then it said:

psql(14102) malloc: *** error for object 0x1807000: incorrect checksum for
freed object - object was probably modified after being freed, break at
szone_error to debug
psql(14102) malloc: *** set a breakpoint in szone_error to debug
zsh: segmentation fault /usr/local/pgsql/bin/psql -U postgres -d sharky

Are you sure this bug report shouldn't be directed to Apple?

regards, tom lane

#3David E. Wheeler
david@kineticode.com
In reply to: Tom Lane (#2)
Re: BUG #1959: readline error exiting psql

On Oct 13, 2005, at 9:54 AM, Tom Lane wrote:

Are you sure this bug report shouldn't be directed to Apple?

Of course it should. I only directed it to you because I had thought
you figured out a workaround for it. If there isn't a workaround, I
won't report it again. :-)

Thanks,

David