From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Francisco Reyes <lists(at)natserv(dot)com> |
Cc: | pgsql General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Troubleshooting cored dumps |
Date: | 2002-04-19 15:58:32 |
Message-ID: | 3CC03EA8.1000108@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 2002-04-19 16:00:38 | Re: Troubleshooting cored dumps |
Previous Message | Francisco Reyes | 2002-04-19 15:50:01 | Troubleshooting cored dumps |