Re: Exited with status 139 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Exited with status 139
Date
Msg-id 24595.970810160@sss.pgh.pa.us
Whole thread Raw
In response to Exited with status 139  (Kristofer Munn <kmunn@munn.com>)
Responses Re: Exited with status 139
List pgsql-hackers
Kristofer Munn <kmunn@munn.com> writes:
> Anyone have any idea what status 139 is?

SIGSEGV, ie, bad pointer dereference.  There should be a core dump
file --- can you provide a stack backtrace from it?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kristofer Munn
Date:
Subject: Exited with status 139
Next
From: Kristofer Munn
Date:
Subject: Re: Exited with status 139