Re: error status 139

Here's more info I was able to track down...

I am making a function call to a c function in my SQL, example:

SELECT funct(arg) FROM x;

Here's the create statment for function func:
CREATE FUCNTION func(path)
  RETURNS point
  AS '${PGLIB}/xxx.so' LANGUAGE 'c';

Inside the c function funct, when a certain condition arises:
...
return NULL;

This is what the backend is SEGVing on, when a NULL gets returned for the function (for the Point type).

Is this correct behaviour of the backend?  Is this how to return a null value for a Point type?

THanks,

L.
On Sat, 21 Jul 2001, Tom Lane wrote:

> Laurette Cisneros <laurette@nextbus.com> writes:
> > Any idea what status 139 indicates?
>
> SIGSEGV core dump, on most systems.  Look for the backend core file
> (in $PGDATA/base/yourdb/core) and send us a gdb stack trace ...
> also, it would help to know what PG version you are running, on
> what platform, and what you were doing when the crash happened.
>
>             regards, tom lane
>

--
Laurette Cisneros
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
Passenger Information Everywhere