Re: BUG #5418: psql exits after using tab-completion with error message

G'day Craig, thanks for your reply.

On 13/04/2010, at 20:33 , Craig Ringer wrote:

>
>> prices=# \d abapsql(11407) malloc: *** error for object 0xe: pointer being
>> freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>> Abort trap
>
> This could be a bug in psql, a buggy/damaged readline library, etc.
>
> For GUI apps Mac OS X makes a crash record in the system logs. I'm not sure if it does that for command line apps too - I think it does. Can you check "Console" and see if there are any crash dumps for psql?

I have checked console, and there are many psql entries - I have attached two as they all appear fairly similar, some numbers changing in this section :

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000002 rcx: 0x00007fff5fbff448 rdx: 0x0000000000000000
rdi: 0x0000000000002efd rsi: 0x0000000000000006 rbp: 0x00007fff5fbff460 rsp: 0x00007fff5fbff448
r8: 0x0000000000000e03 r9: 0x0000000000000000 r10: 0x00007fff868cf8ca r11: 0x0000000000000202
r12: 0x00000001000d5000 r13: 0x00000001000d2000 r14: 0x0000000000000000 r15: 0x0000000000000003
rip: 0x00007fff868d3886 rfl: 0x0000000000000202 cr2: 0x0000000100188bd5

The ones that vary most are rdi, rcx, rbp, cr2 and r15.