cassert was on. Now debug is on, too.
I updated from cvs-head just now.
configure knows it is a linux box.
Should it be trying to link to libwsock32.so
or not? If this is a legitimate link, then
the problem is different than if it is trying
to link it in erroneously.
--elein
The is the top of the config.log
---------------------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by PostgreSQL configure 7.4beta1, which was
generated by GNU Autoconf 2.53. Invocation command line was
$ ./configure --prefix=/local/pghead --with-perl --with-python --enable-depend --enable-cassert --enable-d
ebug
## --------- ##
## Platform. ##
## --------- ##
hostname = cookie
uname -m = i686
uname -r = 2.4.16-4GB
uname -s = Linux
uname -v = #1 Mon Apr 15 08:57:26 GMT 2002
---------------------
$ gdb postmaster
GNU gdb 20010316
Copyright 2001 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-suse-linux"...
(gdb) run -i -D /local/pghead/data
Starting program: /local/pghead/bin/postmaster -i -D /local/pghead/data
Program received signal SIGSEGV, Segmentation fault.
0x40099ac5 in dllname () from /usr/lib/libwsock32.so
(gdb) bt
#0 0x40099ac5 in dllname () from /usr/lib/libwsock32.so
#1 0x081218b1 in StreamServerPort (family=0, hostName=0x0, portNumber=5432, unixSocketName=0x82d6e68 "",
ListenSocket=0x829b420,MaxListen=10) at pqcomm.c:279
#2 0x08150a26 in PostmasterMain (argc=4, argv=0x82cfae8) at postmaster.c:765
#3 0x081233e3 in main (argc=4, argv=0xbffff414) at main.c:215
#4 0x4010e7ee in __libc_start_main () from /lib/libc.so.6
On Mon, Aug 11, 2003 at 11:54:39AM -0400, Tom Lane wrote:
> elein <elein@norcov.com> writes:
> > This is as far as I've gotten with 7.4.
>
> Would you rebuild with --enable-debug (perhaps also --enable-cassert)
> so that the gdb backtrace is more informative?
>
> Also, it seems likely that the issue is in or around the recently-added
> IPv6 support, so I'd suggest using CVS tip or last night's snapshot
> rather than the beta1 tarball. We've already made some portability
> fixes there since beta1.
>
> regards, tom lane
>
