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

Re: BUG #5238: frequent signal 11 segfaults

From: Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-bugs(at)postgresql(dot)org"<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5238: frequent signal 11 segfaults
Date: 2009-12-12 19:08:03
Message-ID: 4B23EA13.1020004@telekom.hu (view raw or flat)
Thread:
Lists: pgsql-bugs
(gdb) p debug_query_string
$1 = 12099472

Now I recompiled pg with --enable-debug and waiting for a new core dump.
I'll post the backtrace and the debug_query_string output ASAP.

Please let me know if there is anything more I can do.

Thanks,

Daniel



Tom Lane wrote:
> Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> writes:
>> (gdb) backtrace
>> #0  0x0000000000453415 in slot_deform_tuple ()
>> #1  0x000000000045383a in slot_getattr ()
>> #2  0x0000000000550dac in ExecHashGetHashValue ()
>> #3  0x0000000000552a98 in ExecHashJoin ()
>> #4  0x0000000000543368 in ExecProcNode ()
>> #5  0x0000000000552aa6 in ExecHashJoin ()
>> #6  0x0000000000543368 in ExecProcNode ()
> 
> Not terribly informative (these binaries are apparently not as
> un-stripped as you thought).  However, this suggests it's a specific
> query going wrong --- "p debug_query_string" in gdb might tell you what.
> Please see if you can extract a test case.
> 
> 			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Robert HaasDate: 2009-12-12 19:17:48
Subject: Re: BUG #5237: strange int->bit and bit->int conversions
Previous:From: Tom LaneDate: 2009-12-12 19:00:20
Subject: Re: BUG #5237: strange int->bit and bit->int conversions

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