Re: How to analyze a core dump
От | S Bob |
---|---|
Тема | Re: How to analyze a core dump |
Дата | |
Msg-id | e5e44ad8-1a41-6813-604a-6fe1c5e4ef90@quadratum-braccas.com обсуждение исходный текст |
Ответ на | Re: How to analyze a core dump (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: How to analyze a core dump
|
Список | pgsql-admin |
On 11/2/20 11:04 AM, Tom Lane wrote: > S Bob <sbob@quadratum-braccas.com> writes: >> On 11/2/20 9:55 AM, Peter Geoghegan wrote: >>> Is signal 10 SIGBUS on your platform? Perhaps check the relevant man >>> page on your platform -- "man signal.7" works for me here. >>> What CPU architecture and operating system are you using? >> 32 bit, Solaris 10 > Solaris should be enough like other Unixen to presume that SIGBUS is 10. > However, that doesn't get you far towards finding a root cause. > > Since you have a core file, maybe you could extract a stack trace > from it? We have some suggestions at > > https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD > > although I'm afraid that's pretty gdb-specific, and Solaris probably > has different debugging tools. > > What PG version are you running, exactly? This client is running Postgres version 9.0.4 I'll have a look at the link you sent, thanks! > > regards, tom lane
В списке pgsql-admin по дате отправления: