Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <41B8D478.3080305@x-ray.at>
Date: Thu, 09 Dec 2004 23:40:56 +0100
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a4) Gecko/20040927
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: PostgreSQL: Bad system call
References: <1102607482 DOT 41b8747a32b4d AT www DOT domainfactory-webmail DOT de>
In-Reply-To: <1102607482.41b8747a32b4d@www.domainfactory-webmail.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Markus Hoenicka schrieb:
> Reini Urban <rurban AT x-ray DOT at> was heard to say:
>>The cause is that the internal cygserver msg buffer is allocated
>>read-only. (IsBadWritePtr() fails)
>>Reason unknown. gcc? cygwin?
>>Solution pending.
>>
>>Szteps to reproduce:
>>cygserver &
>>ipcs
>>=> Bad system call
> 
> Oh great. I'm afraid fixing this is above my head. But at least I'd like to help
> track down the culprit. The interesting fact is that I've downgraded all
> relevant packages that I can think of (PostgreSQL, cygwin1.dll), rebooted the
> box, stopped  cygserver, but still get the error. How can I hose a Cygwin
> installation that not even downgrading helps? What is it that I did not
> downgrade that causes the problem? Does setup.exe keep a log of what I
> precisely up/downgraded?
> 
> I do like PostgreSQL on Unix a lot, but I really hate to ever touch setup.exe
> because more often than not I'm left with a broken database engine.

Corinna just answered to this problem, which I suspected to be a 
cygserver problem, but she said that the caller is responsible for 
allocating the msg buffer, so it should be a postgresql problem.

I'm still scratching my head also, because I'm not really convinced, 
because even cygserver & ipcs fails,
but I'll try to step through this again.


Several people could successfully compile and run the latest postgresql 
See e.g. the postgresql buildfarm with gcc-3.3.3. 
http://www.pgbuildfarm.org/cgi-bin/show_status.pl (Gibbon)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

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