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, 1 Apr 2005 11:04:14 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ipc, sockets and windows sp2 Message-ID: <20050401090414.GD7415@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <424D0232 DOT 5060305 AT smousseland DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <424D0232.5060305@smousseland.com> User-Agent: Mutt/1.4.2i On Apr 1 10:11, Vincent Dedun wrote: > There seems to be odd problems with windows sp2 (and some sp1 with > undetermined updates). Never heard of Windows sp2. NT4 SP2? 2000 SP2? XP SP2? > I work on windows version of drqueue, which is an opensource distributed > rendering management software (for use with maya rendering for exemple), > designed for unix, so it uses IPC ans sockets. > > The port works well for the most of it, except for the server itself > (the master program). > The unix version has no problem on all this, it works on linux, bsds, irix.. > > Please take a look in the main loop (main function), of this short file : > http://www.drqueue.org/svn/trunk/drqueue/master.c > > basicly, the program do this : > -init config > -load saved database of jobs > -set signals handlers > -get shared memory (IPC shared memory and semaphores) > -fork a consitency checking task (it is not involved in the problem, i > tested) > -bind a port (it's server!) > -then go the usual main loop which forks childs process to accept > connections. > > on windows sp2 (and some sp1 with updates), the master keep yelling a > strange error : > > *** MapViewOfFileEx (0xF10000), Win32 error 487. Terminating. > > error 487 means > "Attempt to access invalid address." Ok, three things here. First, please follow the reporting guidelines on http://cygwin.com/problems.html. Second, did you try a developers snapshot from http://cygwin.com/snapshots? Third, if that's not already mentioned on the problems web page, please try to create a short, brief, concise, simple, as minimal as possible, self-contained testcase which allows to reproduce the problem. 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/