BUG #4397: crash in tab-complete.c - Mailing list pgsql-bugs

From Rudolf Leitgeb
Subject BUG #4397: crash in tab-complete.c
Date
Msg-id 200809031431.m83EVUH6036072@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #4397: crash in tab-complete.c
Re: BUG #4397: crash in tab-complete.c
List pgsql-bugs
The following bug has been logged online:

Bug reference:      4397
Logged by:          Rudolf Leitgeb
Email address:      r.leitgeb@x-pin.com
PostgreSQL version: 8.3.3
Operating system:   OSX Leopard
Description:        crash in tab-complete.c
Details:

When I compiled postgresql for different targets (i386, x86_64, ppc, ppc64)
on my Mac, tab-complete.c gave me a number of warnings, that integers are
converted to pointers. Sure enouugh, psql bombs as soon as I hit the TAB key
...

How to reproduce:

- Compile psql for x86_64. This can be easily done with the following
commands:

CFLAGS="-Os -arch x86_64" LDFLAGS="-arch x86_64" ./configure
--disable-depend  --with-pam  --with-openssl
--prefix=/Users/rleitgeb/pq_x86_64

make

make install

- Then connect to a database with psql and hit tab. gdb will output the
following:

postgres=#
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000809000
0x00000001001fa1dc in fn_complete ()
(gdb) bt
#0  0x00000001001fa1dc in fn_complete ()
#1  0x00000001001fbb26 in rl_complete ()
#2  0x00000001001fbb38 in rl_complete ()
#3  0x00000001001ef07b in el_gets ()
#4  0x00000001001fc0be in readline ()
#5  0x0000000100006aaa in gets_interactive ()
#6  0x000000010000725e in MainLoop ()
#7  0x000000010000a070 in main ()

pgsql-bugs by date:

Previous
From: "Stephen Cuppett"
Date:
Subject: BUG #4396: Trigger event fired "UPDATE" when "DELETE" happening via foreign key
Next
From: Euler Taveira de Oliveira
Date:
Subject: Re: BUG #4397: crash in tab-complete.c