Обсуждение: Exited with status 139

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/

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

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 software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux"...

warning: core file may not match specified executable file.
Core was generated by `/db/pgsql/bin/postgres localhost f'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libcrypt.so.1...done.
Reading symbols from /lib/libnsl.so.1...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libutil.so.1...done.
Reading symbols from /usr/lib/libreadline.so.3...done.
Reading symbols from /lib/libtermcap.so.2...done.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0  0x4013d223 in strncpy (s1=0x8975d60 "", s2=0x402c2d68 "",
n=4294967293)   at ../sysdeps/generic/strncpy.c:82
../sysdeps/generic/strncpy.c:82: No such file or directory.
(gdb) bt
#0  0x4013d223 in strncpy (s1=0x8975d60 "", s2=0x402c2d68 "",
n=4294967293)   at ../sysdeps/generic/strncpy.c:82
#1  0x8110fe5 in varcharout ()
#2  0x808b208 in CopyTo ()
#3  0x808ae4f in DoCopy ()
#4  0x80ec6a8 in ProcessUtility ()
#5  0x80eac88 in pg_exec_query_dest ()
#6  0x80eabe7 in pg_exec_query ()
#7  0x80ebad2 in PostgresMain ()
#8  0x80d61c2 in DoBackend ()
#9  0x80d5da1 in BackendStartup ()
#10 0x80d515a in ServerLoop ()
#11 0x80d4be4 in PostmasterMain ()
#12 0x80ab716 in main ()
#13 0x400f7cb3 in __libc_start_main (main=0x80ab6b0 <main>, argc=5,   argv=0xbffffd14, init=0x8064018 <_init>,
fini=0x812925c<_fini>,   rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffd0c)   at
../sysdeps/generic/libc-start.c:78
(gdb)

Did I do that right?

- K

Kristofer Munn * KMI * 732-254-9305 * AIM KrMunn * http://www.munn.com/

* Kristofer Munn <kmunn@munn.com> [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 Linux support
> (gdb)
> 
> Did I do that right?

Half-way. :)

You need to do a 'up' to get out of strcpy, then do a 'list', then
use the 'print' command to print out any nearby variables like so:

print foo

you may also want to try 'print *foo'

best of luck,
-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."