On 24 Dec 2000 at 01:00 (-0500), Tom Lane wrote:
| Brent Verner <[EMAIL PROTECTED]> writes:
| > here's a post-mortem.
|
| > #0 0x1200ce58c in ExecEvalFieldSelect (fselect=0x1401615c0,
| > econtext=0x14016a030, isNull=0x14016ab31 "", isDone=0x0) at execQual.c:1096
|
| Looks reasonable as far as it goes. Evidently the crash is in the
| heap_getattr macro call at line 1096 of src/backend/executor/execQual.c.
| We need to look at the data structures that macro uses.
| What do you get from
|
| p *fselect
$1 = {type = T_FieldSelect, arg = 0x140169d40, fieldnum = 1, resulttype = 25,
resulttypmod = -1}
| p *econtext
$2 = {type = T_ExprContext, ecxt_scantuple = 0x14016a568,
ecxt_innertuple = 0x0, ecxt_outertuple = 0x0,
ecxt_per_query_memory = 0x1400c5df0, ecxt_per_tuple_memory = 0x1400c6670,
ecxt_param_exec_vals = 0x0, ecxt_param_list_info = 0x140141760,
ecxt_aggvalues = 0x0, ecxt_aggnulls = 0x0}
| p *resSlot->val
Error accessing memory address 0x40141838: Invalid argument.
| p *resSlot->ttc_tupleDescriptor
Error accessing memory address 0x40141848: Invalid argument.
additionally:
(gdb) p result
$4 = 1075058736
(gdb) p *resSlot
Error accessing memory address 0x40141830: Invalid argument.
| BTW, if you didn't configure with --enable-cassert, it'd be a good idea
| to go back and try it that way...
will reconfig/rebuild shortly.
brent
