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

From: Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: 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 11:06:02
Message-ID: AANLkTi=3_TZwbfGXTkD3t2ZyG=ZQ+naCkYgYi2TkBUQJ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I can give you access to my Instance, if you would like to try. you just
need to give me your IP, so that I can white list to allow access.

Thanks,
Bala

On Sat, Nov 27, 2010 at 4:33 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au>wrote:

> On 11/27/2010 06:58 PM, Balamurugan Mahendran wrote:
>
>> (gdb) bt
>> #0 strlen () at ../sysdeps/x86_64/strlen.S:48
>> #1 0x0000000000000000 in ?? ()
>> (gdb)
>> #0 strlen () at ../sysdeps/x86_64/strlen.S:48
>> #1 0x0000000000000000 in ?? ()
>>
>
> Grr. Corrupt stack. That's pretty much a useless backtrace. Thanks for
> trying - sometimes a good backtrace is really useful.
>
> Is there any chance you can simplify your data down to something you can
> post? Chop bits out of the schema and COPY data until you find the smallest
> SQL script that still crashes?
>
> --
> Craig Ringer
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Balamurugan Mahendran 2010-11-27 11:39:35 Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Previous Message Craig Ringer 2010-11-27 11:03:28 Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme