Jason,
Based on your tip, here's what I've teased out of the stackdump:
?? ??:0
?? ??:0
?? ??:0
?? ??:0
?? ??:0
?? ??:0
pgstat_send
/usr/src/postgresql-7.3.1-1/src/backend/postmaster/pgstat.c:1088
-- call to send
pgstat_beterm
/usr/src/postgresql-7.3.1-1/src/backend/postmaster/pgstat.c:389
-- call to pgstat_send
reaper
/usr/src/postgresql-7.3.1-1/src/backend/postmaster/postmaster.c:1641
-- call to CleanupProc(pid, exitstatus)
?? ??:0
ServerLoop
/usr/src/postgresql-7.3.1-1/src/backend/postmaster/postmaster.c:956
-- call to select(nSockets, &rmask, &wmask, (fd_set
*) NULL, &timeout)
PostmasterMain
/usr/src/postgresql-7.3.1-1/src/backend/postmaster/postmaster.c:785
-- call to ExitPostmaster
main /usr/src/postgresql-7.3.1-1/src/backend/main/main.c:210
-- call to PostmasterMain
?? ??:0
?? ??:0
crypt /src/crypt/encrypt.c:321 [file not on my system]
------------
It looks like something bad in TCP-IP part of cleanup.
-----Original Message-----
From: Jason Tishler [mailto:jason@tishler.net]
Sent: Wednesday, February 12, 2003 7:38 AM
To: Seth Rubin
Cc: Pgsql-Cygwin
Subject: Re: [CYGWIN] Latest cygwin always crashing with Postgres
Seth,
On Tue, Feb 11, 2003 at 06:11:43PM -0500, Seth Rubin wrote:
> Also, when not running in debug, postmaster crashes after reporting
> the error. Sadly, the crash does not occur when running within gdb.
If you build a debug-able postgres.exe, then you can you addr2line on the
first function address in the stackdump file to see where you are
crashing. For example (using your posted stackdump):
$ addr2line -e /usr/bin/postgres.exe 008A316D
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
