From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23499 invoked by alias); 24 Sep 2003 18:12:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16239 invoked from network); 24 Sep 2003 14:08:42 -0000 Received: from unknown (HELO redhat.com) (24.131.133.249) by sources.redhat.com with SMTP; 24 Sep 2003 14:08:42 -0000 Received: by redhat.com (Postfix, from userid 201) id 66F3832A8A7; Wed, 24 Sep 2003 10:08:39 -0400 (EDT) Date: Wed, 24 Sep 2003 18:12:00 -0000 From: Christopher Faylor To: gdb-patches@sources.redhat.com, gdb@sources.redhat.com Subject: Re: Problem with COM1 port from with GDB 5.3 under cygwin 1.5.3-1 Message-ID: <20030924140839.GA32577@redhat.com> Mail-Followup-To: gdb-patches@sources.redhat.com, gdb@sources.redhat.com References: <3F7099F4.1010405@macdonnell.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2003-09/txt/msg00531.txt.bz2 On Wed, Sep 24, 2003 at 08:25:18AM +0200, Eli Zaretskii wrote: >If Cygwin wants /dev/com1 instead of com1, are you sure it won't want >/dev/lpt1 instead of lpt1 as well? Not yet. Eventually. >Anyway, is this a Cygwin bug or what? IIRC, Windows supports both >com1 and /dev/com1, so why doesn't Cygwin do that as well? Because cygwin now has the ability to create files called "com1", just like UNIX. The string "com1" does get passed on to the OS but, as a guess, it looks like cygwin isn't doing anything special with the name and doesn't recognize it as anything more than a file. >Also, what happens with versions of Cygwin other than 1.5.x? Could >they be broken by this change? This change should work fine with older versions. I don't think I have the authority to approve it, though. cgf