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 To: cygwin AT cygwin DOT com Subject: Re: MapViewOfFileEx errors disappeared with cygwin1-20040716 snapshot References: <87n01xzci1 DOT fsf AT vzell-de DOT de DOT oracle DOT com> <20040719045351 DOT GA9614 AT trixie DOT casa DOT cgf DOT cx> <878ydgxozc DOT fsf AT vzell-de DOT de DOT oracle DOT com> <20040720114946 DOT GJ11473 AT cygbert DOT vinschen DOT de> From: "Dr. Volker Zell" Date: Tue, 20 Jul 2004 15:53:12 +0200 In-Reply-To: <20040720114946.GJ11473@cygbert.vinschen.de> (Corinna Vinschen's message of "Tue, 20 Jul 2004 13:49:46 +0200") Message-ID: <87briass3b.fsf@vzell-de.de.oracle.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, cygwin32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes >>>>> Corinna Vinschen writes: > You're talking about two different problems here. The "Bad system call" > is a result of either not having $CYGWIN set to contain the word "server", > or a result of Cygserver not running. > The failing assertion in Cygserver seems to be a problem of compiling > Cygserver with a g++ version which has some weird bug. The latest > snapshot still has that problem, apparently. I've just created a new > snapshot, which contains a Cygserver which should work fine. At least > I tried it and it runs w/o assertion *and* I don't see the above > "MIT-SHM extension disabled due to lack of kernel support" message with > that Cygserver. I just checked with cygwin-20040720 and indeed cygserver runs fine again. Well my MapViewOfFileEx errors are still there, but that seems to be a different problem. > Corinna Ciao Volker -- 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/