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

From Balamurugan Mahendran
Subject Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Date
Msg-id AANLkTi=3_TZwbfGXTkD3t2ZyG=ZQ+naCkYgYi2TkBUQJ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme  (Balamurugan Mahendran <balamurugan@adaptavant.com>)
List 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@postnewspapers.com.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
>

pgsql-bugs by date:

Previous
From: Balamurugan Mahendran
Date:
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Next
From: Balamurugan Mahendran
Date:
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme