From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeremy Drake <pgsql(at)jdrake(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on a Ge |
Date: | 2011-09-03 14:23:09 |
Message-ID: | 2242.1315059789@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Jeremy Drake <pgsql(at)jdrake(dot)com> writes:
> ... I'm pretty sure that what it crashed on was
> attempting to access the global external variable CurrentMemoryContext.
Ah-hah, good insight!
> The odd thing is, that the disassembly code between the working and
> non-working was the same, except for the offsets.
The code seems to be fetching a pointer to CurrentMemoryContext from a
PC-relative location; presumably that's a literal that the dynamic
linker is supposed to update at shlib load time. I guess that pointer
is not correctly computed in the other case, or else it's fetching the
wrong pointer value.
> Still, I have no idea why adding an include would cause issues accessing
> CurrentMemoryContext.
Me either, but at least it's something to work from. You might try
diffing the working and non-working -E output from cube.c to see if
there are any changes that obviously affect CurrentMemoryContext.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-09-03 14:35:41 | Re: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on a Ge |
Previous Message | Jeremy Drake | 2011-09-03 05:54:33 | Re: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on a Ge |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-09-03 14:24:40 | Re: pg_upgrade automatic testing |
Previous Message | Greg Smith | 2011-09-03 06:19:14 | Re: PATCH: regular logging of checkpoint progress |