Re: BUG #5238: frequent signal 11 segfaults

Поиск
Список
Период
Сортировка
От Nagy Daniel
Тема Re: BUG #5238: frequent signal 11 segfaults
Дата
Msg-id 4B236563.5060700@telekom.hu
обсуждение исходный текст
Ответ на Re: BUG #5238: frequent signal 11 segfaults  (Craig Ringer <craig@postnewspapers.com.au>)
Список pgsql-bugs
Hi Guys,

Here you are:

nagyd@goldbolt:~$ gdb /usr/local/pgsql/bin/postgres core
GNU gdb 6.8-debian
...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libnss_compat.so.2...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libnss_nis.so.2...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Core was generated by `postgres: randir lovehunter 127.0.0.1(33247)
SELECT                           '.
Program terminated with signal 11, Segmentation fault.
[New process 11764]
#0  0x0000000000453415 in slot_deform_tuple ()
(gdb)
(gdb) backtrace
#0  0x0000000000453415 in slot_deform_tuple ()
#1  0x000000000045383a in slot_getattr ()
#2  0x0000000000550dac in ExecHashGetHashValue ()
#3  0x0000000000552a98 in ExecHashJoin ()
#4  0x0000000000543368 in ExecProcNode ()
#5  0x0000000000552aa6 in ExecHashJoin ()
#6  0x0000000000543368 in ExecProcNode ()
#7  0x0000000000552aa6 in ExecHashJoin ()
#8  0x0000000000543368 in ExecProcNode ()
#9  0x0000000000557251 in ExecSort ()
#10 0x0000000000543290 in ExecProcNode ()
#11 0x0000000000555308 in ExecMergeJoin ()
#12 0x0000000000543380 in ExecProcNode ()
#13 0x0000000000557251 in ExecSort ()
#14 0x0000000000543290 in ExecProcNode ()
#15 0x0000000000540e92 in standard_ExecutorRun ()
#16 0x00000000005ecc27 in PortalRunSelect ()
#17 0x00000000005edfd9 in PortalRun ()
#18 0x00000000005e93a7 in exec_simple_query ()
#19 0x00000000005ea977 in PostgresMain ()
#20 0x00000000005bf2a8 in ServerLoop ()
#21 0x00000000005c0037 in PostmasterMain ()
#22 0x0000000000569b48 in main ()
Current language:  auto; currently asm



Thanks,

Daniel


Craig Ringer wrote:
> On 10/12/2009 5:12 AM, Daniel Nagy wrote:
>> The following bug has been logged online:
>>
>> Bug reference:      5238
>> Logged by:          Daniel Nagy
>> Email address:      nagy.daniel@telekom.hu
>> PostgreSQL version: 8.4.1
>> Operating system:   Debian Lenny 5.0.3 x86_64. Kernel: 2.6.31.6-grsec
>> Description:        frequent signal 11 segfaults
>> Details:
>>
>> I got postgres segfaults several times a day.
>
>
> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
>
> --
> Craig Ringer

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5238: frequent signal 11 segfaults
Следующее
От: Nagy Daniel
Дата:
Сообщение: Re: BUG #5238: frequent signal 11 segfaults