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
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
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2011-09-03 14:24:40|
|Subject: Re: pg_upgrade automatic testing|
|Previous:||From: Greg Smith||Date: 2011-09-03 06:19:14|
|Subject: Re: PATCH: regular logging of checkpoint progress|
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2011-09-03 14:35:41|
|Subject: Re: pgsql: Remove "fmgr.h" include in cube
contrib --- caused crash on a Ge|
|Previous:||From: Jeremy Drake||Date: 2011-09-03 05:54:33|
|Subject: Re: pgsql: Remove "fmgr.h" include in cube contrib ---
caused crash on a Ge |