Re: Troubleshooting cored dumps - Mailing list pgsql-general

From Joe Conway
Subject Re: Troubleshooting cored dumps
Date
Msg-id 3CC03EA8.1000108@joeconway.com
Whole thread Raw
In response to Troubleshooting cored dumps  (Francisco Reyes <lists@natserv.com>)
List 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



pgsql-general by date:

Previous
From: Francisco Reyes
Date:
Subject: Troubleshooting cored dumps
Next
From: Vince Vielhaber
Date:
Subject: Re: Troubleshooting cored dumps