X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F996E5A.60804@cs.utoronto.ca> Date: Thu, 26 Apr 2012 11:48:42 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: How to access /dev/ttyS* ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. 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/. [1] http://cygwin.com/ml/cygwin/2010-01/msg00081.html [2] http://allmybrain.com/2010/04/29/debugging-linux-kernel-modules-with-virtualbox-and-kgdb/ Thoughts? Ryan -- 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