From: Eli Zaretskii <eliz@elta.co.il>
To: Creighton MacDonnell <creighton@macdonnell.ca>
Cc: 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
Date: Wed, 24 Sep 2003 05:24:00 -0000 [thread overview]
Message-ID: <ud6dq66up.fsf@elta.co.il> (raw)
In-Reply-To: <3F7099F4.1010405@macdonnell.ca> (message from Creighton MacDonnell on Tue, 23 Sep 2003 13:07:32 -0600)
> Date: Tue, 23 Sep 2003 13:07:32 -0600
> From: Creighton MacDonnell <creighton@macdonnell.ca>
>
> This patch avoids the Cygwin 1.5.* problem with "com*" port names, while
> still allowing "com*" names to be used in GDB scripts (they get
> translated to "/dev/com?"), and also allows "/dev/ttyS*" and "/dev/com*"
> device names to be used.
>
>
> --- ./gdb/rdi-share/unixcomm.c~ 2002-06-08 14:34:41.000000000 -0600
> +++ ./gdb/rdi-share/unixcomm.c 2003-09-23 12:12:43.703125000 -0600
> @@ -96,7 +96,15 @@
> #define PARPORT2 "/dev/par1"
> #endif
>
> -#if defined(_WIN32) || defined (__CYGWIN__)
> +#if defined (__CYGWIN__)
> +#define SERIAL_PREFIX "/dev/com"
> +#define SERPORT1 "/dev/com1"
> +#define SERPORT2 "/dev/com2"
> +#define PARPORT1 "lpt1"
> +#define PARPORT2 "lpt2"
> +#endif
If Cygwin wants /dev/com1 instead of com1, are you sure it won't want
/dev/lpt1 instead of lpt1 as well?
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?
Also, what happens with versions of Cygwin other than 1.5.x? Could
they be broken by this change?
next prev parent reply other threads:[~2003-09-24 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 19:07 Creighton MacDonnell
2003-09-24 5:24 ` Eli Zaretskii [this message]
2003-09-24 18:09 ` Problem with COM1 port with GDB 5.3 under Cygwin 1.5.* Creighton MacDonnell
2003-09-24 18:12 ` Eli Zaretskii
2003-09-24 20:03 ` Problem with COM1 port with GDB 5.3 under cygwin 1.5.* Christopher Faylor
2003-09-25 4:46 ` Eli Zaretskii
2003-09-24 18:12 ` Problem with COM1 port from with GDB 5.3 under cygwin 1.5.3-1 Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 11:54 Problem with COM1 port from with GDB 5.3 under Cygwin 1.5.3-1 Thomas Doerfler
2003-09-10 14:55 ` Creighton MacDonnell
2003-09-10 15:18 ` Thomas Doerfler
2003-09-10 16:48 ` Creighton MacDonnell
2003-09-10 18:55 ` Thomas Doerfler
2003-09-10 18:56 ` Problem with COM1 port from with GDB 5.3 under cygwin 1.5.3-1 Christopher Faylor
2003-09-10 20:05 ` Creighton MacDonnell
2003-09-10 21:58 ` Christopher Faylor
2003-09-08 21:41 Problem with COM1 port from with GDB 5.3 under Cygwin 1.5.3-1 Creighton MacDonnell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ud6dq66up.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=creighton@macdonnell.ca \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).