Re: SIGSEGV taken on 8.1 during dump/reload - Mailing list pgsql-hackers

From Robert Creager
Subject Re: SIGSEGV taken on 8.1 during dump/reload
Date
Msg-id 20051107080714.5d5680b0@thunder.logicalchaos.org
Whole thread Raw
In response to Re: SIGSEGV taken on 8.1 during dump/reload  (Robert Creager <Robert_Creager@LogicalChaos.org>)
Responses Re: SIGSEGV taken on 8.1 during dump/reload
List pgsql-hackers
When grilled further on (Sun, 6 Nov 2005 20:00:38 -0700),
Robert Creager <Robert_Creager@logicalchaos.org> confessed:

Didn't set the core big enough (1Mb).  It's now at 50Mb.

I am using PGSphere, which should be the only gist indexes in use.

gdb /usr/local/pgsql810/bin/postgres core.28053
...
warning: core file may not match specified executable file.
Core was generated by `postgres: robert tassiv [local] CREATE INDEX              '.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Cannot access memory at address 0x400d8000
#0  0x08082057 in gistUserPicksplit (r=Cannot access memory at address
0xbfffcb28
) at gistutil.c:833
833             if (v->spl_right[v->spl_nright - 1] == InvalidOffsetNumber)
(gdb) bt
#0  0x08082057 in gistUserPicksplit (r=Cannot access memory at address
0xbfffcb28
) at gistutil.c:833
Cannot access memory at address 0xbfffcb3c


Unfortunately, I have to run shortly.  If someone want's a 1Mb core, I have one.I'll have (presumably) more info this
eveningwith the bigger core, 

Cheers,
Rob
-- 07:56:01 up 36 days, 30 min,  7 users,  load average: 2.25, 2.31, 2.23
Linux 2.6.5-02 #8 SMP Mon Jul 12 21:34:44 MDT 2004

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: parameterized limit statements
Next
From: Sreejesh O S
Date:
Subject: Access CVS