Re: Troubleshooting cored dumps

Поиск
Список
Период
Сортировка
От Joe Conway
Тема Re: Troubleshooting cored dumps
Дата
Msg-id 3CC03EA8.1000108@joeconway.com
обсуждение исходный текст
Ответ на Troubleshooting cored dumps  (Francisco Reyes <lists@natserv.com>)
Список 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 по дате отправления:

Предыдущее
От: Francisco Reyes
Дата:
Сообщение: Troubleshooting cored dumps
Следующее
От: Vince Vielhaber
Дата:
Сообщение: Re: Troubleshooting cored dumps