X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 8 Mar 2012 17:16:13 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Anamoly with ioctl() in cygwin 1.7.10 Message-ID: <20120308161613.GY5159@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20120308103354 DOT GU5159 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20120308103354.GU5159@calimero.vinschen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 8 11:33, Corinna Vinschen wrote: > On Mar 8 01:35, Lee Collier wrote: > > Jon Clugston gmail.com> writes: > > > > > > Don't know if it will fix your problem, but you cannot just create a > > > mutex on the stack and call "lock" on it. You must initialize it with > > > "pthread_mutex_init()". > > > > > > Jon > > > > > > > > Good catch. I missed that in my haste to scrounge a sample pgm together. With or > > w/out initializing the mutex the anomaly still occurs. > > You're trying this on a 64 bit machine, right? Call `peflags -l0' on > your executable and try again. It should work. > > This is terribly annoying. While the executables are large address aware, > the operating system apparently is not! > > What happens is that the function GetAdaptersAddresses fails, because > it's running on a thread stack in the large address area. It doesn't > matter if the addresses given to the function are in the large address > area or not. It's sufficent that the stack is there. I'm not holy > myself, but this is really, really bad programming. Grrr. > > But that doesn't help, of course. I'll try to come up with a solution. Well, I think I have a solution now. I applied a patch to CVS and I'm just generating a new developer snapshot. Please give the today's snapshot from http://cygwin.com/snapshots/ a try. Oh, and, thanks for the report and the testcase. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple