First, I appologize if this is not the correct list for this :).

Ive had a crash occur in postgres 7.0.2. When the db crashed, there was quite a
bit going on, so I am not really sure what caused it.  As such, I cant really
reproduce this :(.  The only thing that I have that might help you guys is the
core file.  Below is a backtrace from the core file.

Anyways, I thought I should at least post what I hqve here in case this is
useful to the backend hackers :).

The system this is running on is:

Linux 2.2.14

Dual P-III 500 MHz.
768 MB ram.

I ran the core file through gdb and got a backtrace that looks like this:

[root@testbed mschout]# gdb postmaster core
GNU gdb 19991004
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"...
(no debugging symbols found)...
Core was generated by `/usr/bin/postgres localhost postgres'.
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.
Reading symbols from /lib/libnss_compat.so.2...done.
Reading symbols from /lib/libnss_files.so.2...done.
Reading symbols from /usr/lib/gconv/ISO8859-1.so...done.
#0  0x0 in ?? ()
(gdb) bt
#0  0x0 in ?? ()
#1  0x401029e6 in getenv (name=0x1 <Address 0x1 out of bounds>)
    at ../sysdeps/generic/getenv.c:77
#2  0x80f2074 in quickdie ()
#3  0x40100408 in __ldexpf (value=2.4801743, exp=1074648272)
    at ../sysdeps/libm-ieee754/s_ldexpf.c:30
#4  0x4000a120 in _dl_map_object_deps (map=0x4000a120, preloads=0x40012024, 
    npreloads=3221220516, trace_mode=1073815588, global_scope=-1073746744)
    at dl-deps.c:257
#5  0x400ceaf5 in _nc_parse_entry () from /usr/lib/libncurses.so.4
#6  0x4000a6a6 in _dl_map_object_deps (map=0xbfffecb0, preloads=0x20657661, 
    npreloads=1074647000, trace_mode=10, global_scope=1) at dl-deps.c:542
#7  0x401029e6 in getenv (name=0x1 <Address 0x1 out of bounds>)
    at ../sysdeps/generic/getenv.c:77
#8  0x80f2074 in quickdie ()
#9  0x40100408 in __ldexpf (value=0, exp=135961688)
    at ../sysdeps/libm-ieee754/s_ldexpf.c:30
#10 0x80aea87 in pq_getbytes ()
#11 0x80f1b6c in HandleFunctionRequest ()
#12 0x80f1c07 in HandleFunctionRequest ()
#13 0x80f2e2d in PostgresMain ()
#14 0x80dbea2 in PostmasterMain ()
#15 0x80db9ea in PostmasterMain ()
#16 0x80dad36 in PostmasterMain ()
#17 0x80da7ac in PostmasterMain ()
#18 0x80af655 in main ()
#19 0x400fa1eb in ?? () from /lib/libc.so.6
(gdb) 



Sat, 8 Jul 2000 10:49:47 -0500 (CDT)
Michael J Schout <mschout@gkg.net>
crash in 7.0.2...
Michael J Schout <mschout@gkg.net> writes:
> Ive had a crash occur in postgres 7.0.2. When the db crashed, there
> was quite a bit going on, so I am not really sure what caused it.  As
> such, I cant really reproduce this :(.  The only thing that I have
> that might help you guys is the core file.  Below is a backtrace from
> the core file.

Unfortunately I don't think I believe the backtrace at all :-(.
quickdie does not call getenv, for example.  I think gdb has probably
gotten confused and printed garbage information.

You might want to recompile the backend with -g, in hopes of getting
a more useful backtrace if it happens again.

			regards, tom lane

Sat, 08 Jul 2000 13:00:06 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: crash in 7.0.2... 