X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6B6A69FACFE; Thu, 27 Jul 2006 20:27:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 68439-02; Thu, 27 Jul 2006 20:26:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 75BBB9FB1FB; Thu, 27 Jul 2006 20:26:18 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6RNQ6mE014156; Thu, 27 Jul 2006 19:26:06 -0400 (EDT) To: "Daniel Caune" cc: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] PostgreSQL server terminated by signal 11 In-reply-to: <1E293D3FF63A3740B10AD5AAD88535D202B64F64@UBIMAIL1.ubisoft.org> References: <1E293D3FF63A3740B10AD5AAD88535D202B64F64@UBIMAIL1.ubisoft.org> Comments: In-reply-to "Daniel Caune" message dated "Thu, 27 Jul 2006 19:00:27 -0400" Date: Thu, 27 Jul 2006 19:26:06 -0400 Message-ID: <14155.1154042766@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.036 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/248 X-Sequence-Number: 22494 "Daniel Caune" writes: > I run the command responsible for creating the index and I entered "continue" in gdb for executing the command. After a while, the server crashes: > Program received signal SIGSEGV, Segmentation fault. > 0x08079e2a in slot_attisnull () > (gdb) > Continuing. > Program terminated with signal SIGSEGV, Segmentation fault. > The program no longer exists. > I can't do "bt" since the program no longer exists. I think you typed one carriage return too many and the thing re-executed the last command, ie, the continue. Try it again. The lack of arguments shown for slot_attisnull suggests that all we're going to get is a list of function names, without line numbers or argument values. If that's not enough to figure out the problem, can you rebuild with --enable-debug to get a more useful stack trace? regards, tom lane