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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 14 Feb 2002 10:59:11 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Lego IR tower USB driver vs. Cygwin Message-ID: <20020214105911.S23094@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020214195624 DOT 00a03ec0 AT mail DOT mckinn1 DOT vic DOT optushome DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20020214195624.00a03ec0@mail.mckinn1.vic.optushome.com.au> User-Agent: Mutt/1.3.22.1i On Thu, Feb 14, 2002 at 08:26:49PM +1100, Graham Menhennitt wrote: > The download program attempts to open a device named \\.\legotower1. This > works via the standard Win32 call CreateFile(). However, under Cygwin, the > effect is quite strange. When you try to open the device using: > open("\\\\.\\legotower1, O_RDWR) > the machine hangs for a considerable period (~30 seconds). In this time, > the machine is essentially dead - the mouse cursor moves but the cursor in > [...] > I've tried debugging it to see the exact parameters that open() eventually > uses when it internally calls CreateFIle() - so far no success. Sounds as if Cygwin tries to access a network drive for some reason... unfortunately devices and SMB paths are both using leading double backslashes so there's room for misinterpretation. If you run your app under strace you can probably find a line where suddenly the timestamp jumps to a very big value. That's a good starting point for further debugging with gdb. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/