postmaster crashing

I have been trying to find out more about the postmaster crashing, but
things seem to be getting stranger! I am experiencing problems running
postmaster in gdb too (see end of message)

I will put all the information in this posting for completness,
apologies for the duplicated sections.

I am running postgresql 7.3.4 on ia64 Red Hat Advance Server 3 beta.
Now compiled from 7.3.4 source downloaded from postgresql.org.

Tsearch2 compiled from tsearch-v2-stable.tar.gz

I am very stuck so thank you for any ideas or guesses about whats
happening or how to further research the problem.

Potentially useful output below (in the order i did it):

cd postgresql7.3.4_src_dir
./configure --enable-debug
<- rest of install process from top of readme ->

<- tsearch2 compile/install ->

initdb on /data
createdb test

<- create a table in test and populate it with test data ->
<- query test data sucessfully ->

test# SELECT 'Our first string used today'::tsvector;
tsvector
---------------------------------------
'Our' 'used' 'first' 'today' 'string'
(1 row)

test=# SELECT to_tsvector( 'default', 'this is many words' );
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!#


LOG: server process (pid 7698) was terminated by signal 11
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing shared memory and
semaphores
LOG: database system was interrupted at 2003-09-02 13:26:42 UTC
LOG: checkpoint record is at 0/967458
LOG: redo record is at 0/967458; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 581; next oid: 25098
LOG: database system was not properly shut down; automatic recovery in
progress
FATAL: The database system is starting up
LOG: ReadRecord: record with zero length at 0/9674A0
LOG: redo is not required
LOG: database system is ready

<-shutdown backend ->

After more poking i discovered that the to_tsvector function call does
not cause a seg fault in the backend if you pass it only numbers,
characters and whitespace, but instead works as desired.

ddd postmaster
<- run postmaster with -D /data ->

psql test
<- seg fault, similar LOG message to above but now with signal 5 ->

psql db_that_not_exist
<- seg fault as previous ->


How do i get the core files to examine? There never seem to be any
produced, even outside the debuggers. I can't even connect to the db
when its running in the debugger

Thanks for reading this far,
Grateful for any help or sugestions,
Matt

--