Re: Troubleshooting cored dumps

Joe Conway <mail@joeconway.com>

From: Joe Conway <mail@joeconway.com>
To: Francisco Reyes <lists@natserv.com>
Cc: pgsql General List <pgsql-general@postgresql.org>
Date: 2002-04-19T15:58:32Z
Lists: pgsql-general
Francisco Reyes wrote:
> How does one go about troubleshooting Core Dumps?
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> server sent data ("D" message) without prior row description ("T" message)
> DEBUG:  pq_flush: send() failed: Broken pipe
> Segmentation fault (core dumped)
> 

run:
gdb [options] [executable-file [core-file or process-id]]

Assuming you're in the directory with the core, it would look something 
like:

gdb /usr/local/pgsql/bin/postgres ./core

Once in gdb, run the command "bt" to see a backtrace.

However if you haven't compiled PostgrSQL with --enable-debug, it will 
be difficult to tell what was going on.


HTH,

Joe