Tracking down core dump in 642.

Поиск
Список
Период
Сортировка
От christian
Тема Tracking down core dump in 642.
Дата
Msg-id Pine.LNX.4.10.9905212123580.3407-100000@violinux.apocalypse.now
обсуждение исходный текст
Список pgsql-general
I'm trying (once more) to get 6.4.2. to run here. Symptoms are: after
installation and initdb, psql SEGVs when run.

Can I enable -g (and no -O2) in configure, or do I have to do this
manually? I've run a gdb on the non-debug version of psql, which tells me
very little (or at least, nothing I didn't expect):

(gdb) r
Starting program: /usr/local/pgsql/bin/psql

Program received signal SIGSEGV, Segmentation fault.
0x8053563 in pqWait ()
(gdb) where
#0  0x8053563 in pqWait ()
#1  0x805027d in connectDB ()
#2  0x815b0000 in ?? ()
Cannot access memory at address 0xe853.

Seems like a buffer overrun somewhere. I'll be back on this.

6.5beta runs fine here, but since it's beta and I'd like to see production
6.4.2 running, 'I'm trying'.

cr


В списке pgsql-general по дате отправления:

Предыдущее
От: reedstrm@wallace.ece.rice.edu (Ross J. Reedstrom)
Дата:
Сообщение: Re: [GENERAL] Relations between tables.
Следующее
От: Piotr Stelmaszyk
Дата:
Сообщение: PL/pgSQL - mailng list