Kristofer Munn <[EMAIL PROTECTED]> 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
- [HACKERS] Exited with status 139 Kristofer Munn
- Re: [HACKERS] Exited with status 139 Tom Lane
- Re: [HACKERS] Exited with status 139 Kristofer Munn
- Re: [HACKERS] Exited with status 139 Alfred Perlstein