delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Thu, 8 Mar 2012 11:33:54 +0100 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Anamoly with ioctl() in cygwin 1.7.10 |
Message-ID: | <20120308103354.GU5159@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <CALAQL3J43=MA-fFHSd-VVyuJ_n1cpAuEQ1zpxvrRDXptQk8sSQ AT mail DOT gmail DOT com> <CAG_2cTm5JXFsiK0MaUQr36pxVFNeAmsNpGTo65q9inRB=U5e4w AT mail DOT gmail DOT com> <loom DOT 20120308T023115-96 AT post DOT gmane DOT org> |
MIME-Version: | 1.0 |
In-Reply-To: | <loom.20120308T023115-96@post.gmane.org> |
User-Agent: | Mutt/1.5.21 (2010-09-15) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
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 |
On Mar 8 01:35, Lee Collier wrote: > Jon Clugston <jon.clugston <at> 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. 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |