Re: [HACKERS] Exited with status 139

2000-10-05 Thread Alfred Perlstein
* Kristofer Munn <[EMAIL PROTECTED]> [001005 22:41] wrote: > On Fri, 6 Oct 2000, Tom Lane wrote: > > > SIGSEGV, ie, bad pointer dereference. There should be a core dump > > file --- can you provide a stack backtrace from it? > > I can try: > > # gdb bin/postgres core > GNU gdb 4.17.0.11 with L

Re: [HACKERS] Exited with status 139

2000-10-05 Thread Kristofer Munn
On Fri, 6 Oct 2000, Tom Lane wrote: > SIGSEGV, ie, bad pointer dereference. There should be a core dump > file --- can you provide a stack backtrace from it? I can try: # gdb bin/postgres core GNU gdb 4.17.0.11 with Linux support Copyright 1998 Free Software Foundation, Inc. GDB is free softwa

Re: [HACKERS] Exited with status 139

2000-10-05 Thread Tom Lane
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

2000-10-05 Thread Kristofer Munn
I got a message in my syslog stating: Server process (pid 26969) exited with status 139 at Thu Oct 5 03:02:21 2000 It disconnected all other active processes, etc. Anyone have any idea what status 139 is? - K Kristofer Munn * KMI * 732-254-9305 * AIM KrMunn * http://www.munn.com/