Skip site navigation (1) Skip section navigation (2)

Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Date: 2010-11-27 10:55:59
Message-ID: 4CF0E3BF.9010203@postnewspapers.com.au (view raw or flat)
Thread:
Lists: pgsql-bugs
On 11/27/2010 05:45 PM, Balamurugan Mahendran wrote:
> YES, Its on Amazon EC2 (our production DB running postgres 8.3 version
> for more than 3yrs). And its a clean folder.

OK, thanks.

> Core was generated by `postgres: postgres acti [local] COPY '.
> Program terminated with signal 11, Segmentation fault.
> [New process 16223]
> #0  strlen () at ../sysdeps/x86_64/strlen.S:48
> 48      ../sysdeps/x86_64/strlen.S: Permission denied.
>          in ../sysdeps/x86_64/strlen.S
> (gdb)

Here, you need to type:

    bt

and press enter. That requests the backtrace that shows the function 
calls leading up to the crash. Without that all we know is that it 
crashed in strlen(), which isn't very useful since it was probably a 
null pointer dereference caused by an argument passed to it from elsewhere.

--
Craig Ringer

In response to

Responses

pgsql-bugs by date

Next:From: Balamurugan MahendranDate: 2010-11-27 10:58:06
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Previous:From: Balamurugan MahendranDate: 2010-11-27 09:45:20
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group