Re: [HACKERS] Strange pgsql crash on MacOSX

2006-12-28 Thread Tom Lane
I wrote: > The source code available from Apple shows that they got this code from > NetBSD originally > /*$NetBSD: history.c,v 1.25 2003/10/18 23:48:42 christos Exp $*/ > so this may well be a pretty generic *BSD bug. Anyone clear on who to > report it to? I have no idea if libedit is an

Re: [HACKERS] Strange pgsql crash on MacOSX

2006-12-28 Thread Tom Lane
Shane Ambler <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Hm, so the question is: is it our bug or Apple's? If you kept the >> busted history file, would you be willing to send me a copy? > The zip file attached has the psql_history file that crashes when > quiting but doesn't appear to cont

Re: [HACKERS] Strange pgsql crash on MacOSX

2006-12-23 Thread Tom Lane
Shane Ambler <[EMAIL PROTECTED]> writes: > I just found out the problem. > psql_history - I had tried to copy from a text file earlier that was > utf8 and came up with some errors, I guess these got into the history > file and stuffed it up. Hm, so the question is: is it our bug or Apple's? If

Re: [HACKERS] Strange pgsql crash on MacOSX

2006-12-23 Thread Shane Ambler
Shane Ambler wrote: Tom Lane wrote: Shane Ambler <[EMAIL PROTECTED]> writes: postgres=# \q psql(24931) malloc: *** error for object 0x180a800: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug psql(24931) malloc: *** set a breakp

Re: [HACKERS] Strange pgsql crash on MacOSX

2006-12-22 Thread Tom Lane
Shane Ambler <[EMAIL PROTECTED]> writes: > postgres=# \q > psql(24931) malloc: *** error for object 0x180a800: incorrect checksum > for freed object - object was probably modified after being freed, break > at szone_error to debug > psql(24931) malloc: *** set a breakpoint in szone_error to debug >

[HACKERS] Strange pgsql crash on MacOSX

2006-12-22 Thread Shane Ambler
I have a dual G4 1.25Ghz with 2GB RAM running Mac OSX 10.4.8 and PostgreSQL 8.2.0 This only happened to me today and with everything I have tried it always happens now - had been running fine before. The only thing I can think of that has changed in the last few days is I have installed the la