X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 26 Apr 2012 22:04:51 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: How to access /dev/ttyS* ?
Message-ID: <20120426200451.GD28119@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4F996E5A DOT 60804 AT cs DOT utoronto DOT ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F996E5A.60804@cs.utoronto.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Apr 26 11:48, Ryan Johnson wrote:
> Hi all,
> 
> I'm trying to connect a VirtualBox guest's serial port to something
> that cygwin/gdb can access for remote debugging, and am having
> trouble connecting the pieces...
> 
> One post from a couple of years ago [1] suggests using /dev/ttyS* to
> access COM ports. This would work great... except there are no
> /dev/ttyS* on my install.

If the VM has a virtual HW serial port configured, you should see a
/dev/ttyS0 entry.  If it's not there, you didn't configure it.  Cygwin
in the guest can only access what is available in the guest OS.  If
there's a COM1, Cygwin has a /dev/ttyS0.

> The other VirtualBox option is to create a named pipe (as in Windows
> NPFS), and then wrap it into a pty using socat [2], but I can't
> figure out how to access such a pipe from cygwin -- the "\\.\pipe\*"
> path doesn't seem to be supported by cygpath and there's nothing
> obvious in /dev/.

I don't know how that's supposed to work, but you could try to
connect it via /proc/sys/Device/NamedPipe/<name-of-named-pipe>
No guarantee that it works, though.


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