v6.3 snapshot core dump

From: Brett McCormick <brett(at)techno(dot)chicken(dot)org>
To: pgsql-hackers(at)hub(dot)org
Subject: v6.3 snapshot core dump
Date: 1998-02-13 11:19:44
Message-ID: 199802131119.DAA10021@abraxas.scene.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


this is the latest snapshot under linux 2.0.33

when I create a view with an aggregate such as count (with a group by
clause) I get a core dump. The first three lines of the gdb backtrace
follows:

#0 0x80a9982 in ExecEvalAggreg (agg=0x820fa20, econtext=0x8213a48,
isNull=0xbfffd6cf "") at execQual.c:201
#1 0x80ab271 in ExecEvalExpr (expression=0x820fa20, econtext=0x8213a48,
isNull=0xbfffd6cf "", isDone=0xbfffd7c3 "\001\fZ\031\b\030K!\b")
at execQual.c:1199
#2 0x80ab69b in ExecTargetList (targetlist=0x8213498, nodomains=2,
targettype=0x8214990, values=0x8214b48, econtext=0x8213a48,
isDone=0xbfffd7c3 "\001\fZ\031\b\030K!\b") at execQual.c:1484

code at point:

201 *isNull = econtext->ecxt_nulls[agg->aggno];

econtext->ecxt_nulls, is, well, a NULL pointer and hard to index :)
i'll take a look but I don't think I'll find it -- i notice that 6.2.1
pretends to make a view with aggregates but then it comes up empty
when selected.

--brett
let me know if you need more info

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Frederick W. Reimer 1998-02-13 11:24:12 Re: [PORTS] v6.3 release ToDo list and supported ports
Previous Message Maurice Gittens 1998-02-13 11:05:57 Memory leaks?