Re: 7.2.1 segfaults.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Amadei <amadei(at)dandy(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.2.1 segfaults.
Date: 2002-05-04 03:43:52
Message-ID: 24506.1020483832@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Stephen Amadei <amadei(at)dandy(dot)net> writes:
>> Urgh. Can you provide a stack trace?

> You mean using strace? Yeah. The strace created quite a bit of logs, but
> the process that segfaulted is included below.

> open("/usr/local/pgsql/data/global/1262", O_RDONLY) = 4
> read(4, "\0\0\0\0\f\222\20\0\7\0\0\0\34\0\244\37\0 \0 \244\37\0"..., 8192) = 8192
> --- SIGSEGV (Segmentation fault) ---

Hmm, this does not square with your prior statement that it's a chroot
can't-call-/bin/cp issue. Would you set things up to allow a core dump
(ie, not ulimit -c 0) and then do "gdb postgres-executable corefile"
followed by "bt"?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Amadei 2002-05-04 04:14:38 Re: 7.2.1 segfaults.
Previous Message Tom Lane 2002-05-04 03:37:04 Re: Why does Postgres need the /bin/sh?