Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 10 Dec 2004 15:05:53 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: PostgreSQL: Bad system call Message-ID: <20041210140553.GH22056@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1102607482 DOT 41b8747a32b4d AT www DOT domainfactory-webmail DOT de> <41B8D478 DOT 3080305 AT x-ray DOT at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41B8D478.3080305@x-ray.at> User-Agent: Mutt/1.4.2i On Dec 9 23:40, Reini Urban wrote: > 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. That would be helpful. Note that I did *not* say that cygserver/cygwin can't be blamed. I just don't see (so far perhaps) how that could be possibly the case. Just today I tried a message queue testcase(tm) and ipcs successfully with cygwin 1.5.12 + accompanying tools. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT 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/