From:	D DOT J DOT Fiddes AT hw DOT ac DOT uk ("David Fiddes")
Subject:	Re: Opening COM2
7 Apr 1997 09:47:56 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199704071538.QAA01957.cygnus.gnu-win32@ma.hw.ac.uk>
Mime-Version:	1.0
Original-To:	<gnu-win32 AT cygnus DOT com>
X-MSMail-Priority:	Normal
X-Priority:	3
X-Mailer:	Microsoft Internet Mail 4.70.1161
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

> My guess is that this is due to the symbolic link handling.
> When you open a file, cygwin will read the first few bytes
> of the file to see if it has the special marker that is used
> to indicate a symbolic link; if so, then cygwin will open the
> file that the link points to.  Obviously this won't work
> correctly in the case of device files such as `com2'...
> 

Would this cause GDB to hang when trying to connect to a target "monitor"
on a development board. GDB seems to support(from it's list of targets and
the source) my monitor(dBUG for ColdFire) but it hangs when I type "target
dbug com2" (the default port settings for COM2 are OK). I haven't stuck a
terminal or a protocol analyser on it yet.....

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -