Re: Postmaster core dumps

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Aug  3 17:17, Novaelec wrote:
> Hello Corinna,
> 
> I think the problem is in cygserver because the bug is related to semaphores
> when I use gdb.
> 
> Here you have a case where you get the error:
> 
> First, you must install postgresql (ver. 7) with Cygwin installation. Later,
> configure the database:
> 
> $ /usr/sbin/cygserver&
> 
> $ export CYGWIN=server
> 
> $ initdb -D /usr/local/pgsql/data -W -E LATIN1
> 
> And now comes the problem:
> 
> $ postmaster -D /usr/local/pgsql/data
> 
> It returns "segmentation fault (core dumped)".

That's not what I meant.  I ws talking about minimum source code which
allows to reproduce the problem.

> Any idea?

Sorry to say that, but to me it looks like a bug in postmaster.  Looking
into the stacktrace printed when the SEGV occurs, I'm getting this:

$ addr2line -e /bin/cygwin1.dll 610D6127 610028FE 610173A9 61017A6E 61017D1F 6109E76C 610942FF
/home/corinna/src/cygwin/vanilla/newlib/libc/machine/i386/memset.S:45
/home/corinna/src/cygwin/vanilla/winsup/cygwin/cygheap.cc:331
/home/corinna/src/cygwin/vanilla/winsup/cygwin/dtable.cc:375
/home/corinna/src/cygwin/vanilla/winsup/cygwin/dtable.cc:486
/home/corinna/src/cygwin/vanilla/winsup/cygwin/dtable.cc:532
/home/corinna/src/cygwin/vanilla/winsup/cygwin/syscalls.cc:127

This is the stacktrace of a dup() call on the tty slave descriptor.  It
looks like a heap corruption to me.  It has certainly nothing to do with
semaphores.

I'd rather like to see somebody who knows postmaster to debug it to the
point where the SEGV occurs and to create a minimum testcase (see above)
if possible.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/