Re: Segmentation fault after upgrading to 1.5.18-1 - Mailing list pgsql-cygwin

From Jason Tishler
Subject Re: Segmentation fault after upgrading to 1.5.18-1
Date
Msg-id 20050711133226.GF3856@tishler.net
Whole thread Raw
In response to Segmentation fault after upgrading to 1.5.18-1  (Sebastiano Pilla <etechweb@yahoo.com>)
Responses Re: Segmentation fault after upgrading to 1.5.18-1  (Jason Tishler <jason@tishler.net>)
List pgsql-cygwin
Sebastiano,

On Sat, Jul 09, 2005 at 10:17:55AM +0000, Sebastiano Pilla wrote:
> Hi, yesterday I upgraded my cygwin on Windows XP to the 1.5.18-1
> version, and now the previously installed postmaster (7.4.5-1) doesn't
> start anymore. It was working fine before the upgrade.
>
> [snip]
>
> And here's the stackdump:
>
> admin@DATA ~
> $ cat postgres.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=610028AA
> eax=00000000 ebx=61258F10 ecx=00000030 edx=000001A8 esi=000001A8 edi=61259000
> ebp=0022E948 esp=0022E910 program=D:\cygwin\bin\postgres.exe, pid 3672, thread
> main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022E948  610028AA  (00000000, 61258D10, 0022E978, 6101F5E8)

The above indicates that PostgreSQL is crashing inside of the Cygwin
DLL.  Unfortunately, one cannot conclude whether the bug is in Cygwin or
PostgreSQL without further debugging.  FWIW, Cygwin 1.5.18-1 has a newer
version of Doug's Lea malloc which is more sensitive to problem like
double-free errors.  See the Cygwin mailing list for more details, if
interested.

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

pgsql-cygwin by date:

Previous
From: "Ian Oxley"
Date:
Subject: Recall: initdb 'no such file or directory' error
Next
From: "Support"
Date:
Subject: Problem with Cygwin 1.5.18