public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Postmaster core dumps
Date: Wed, 10 Aug 2005 19:47:00 -0000	[thread overview]
Message-ID: <20050810194723.GD6294@trixie.casa.cgf.cx> (raw)
In-Reply-To: <ABA3C1378EE5A147B765295B0893C9A21054D2@novaelecserver.novaelec.com>

On Mon, Aug 08, 2005 at 07:18:26PM +0200, depinfo - Dep. Informatica wrote:
>Hi!
>
>Wonderful! PostgreSQL works again! :) Thanks a lot!
>
>But I've detected a little error that also was present before. Prior to
>start PostgreSQL is necessary run "$ cygserver" and to finish a session
>is necessary to stop the server, so anybody can use "$ cygserver -S" to
>do that. Well, but that command produces the next error:
>
>Segmentation fault (core dumped).
>
>And using gdb:
>
>Program received signal SIGSEGV, Segmentation fault.
>
>0x0040644c in create_server_transport () at
>/netrel/src/cygwin-snapshot-20050808-1/winsup/cygwin/wincap.h:84
>
>84 in /netrel/src/cygwin-snapshot-20050808-1/winsup/cygwin/wincap.h
>
>Another option is kill the process, but I think that the argument -S is
>better (more beautiful maybe :D) and would be used instead.
>
>Anyway, I thought I could make any changes by myself, but I don't know
>how... how could I see the code? Could I fix anything by myself?

This should be fixed in the latest snapshot:

http://cygwin.com/snapshots/

cgf

--
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/

  reply	other threads:[~2005-08-10 19:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 17:20 depinfo - Dep. Informatica
2005-08-10 19:47 ` Christopher Faylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-11 16:31 depinfo - Dep. Informatica
2005-08-11  7:11 depinfo - Dep. Informatica
2005-08-11 14:27 ` Christopher Faylor
2005-08-04 16:50 Igor Pechtchanski
2005-08-04 17:17 ` Novaelec
     [not found] <0MKu60-1E0L272OZO-0000t4@mxeu10.kundenserver.de>
2005-08-03 15:40 ` Corinna Vinschen
2005-08-04 13:10   ` Corinna Vinschen
2005-08-04 16:17     ` Novaelec
2005-08-07  3:18     ` Christopher Faylor
2005-08-08  4:46       ` Jon A. Lambert
2005-08-03 15:19 Novaelec
2005-07-19 13:39 Novaelec
2005-07-19 11:22 Jason Tishler
2005-07-18 20:06 Reini Urban
2005-08-01 14:20 ` Corinna Vinschen
2005-07-18 17:38 Novaelec
2005-07-18 12:24 Jason Tishler
2005-07-18 12:08 Novaelec
2005-07-15 16:11 Frank-Michael Moser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050810194723.GD6294@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).