From mboxrd@z Thu Jan  1 00:00:00 1970
From: "William A. Gatliff" <bgat@saturn.billgatliff.com>
To: cygwin@cygwin.com, gdb@sources.redhat.com
Subject: Re: [1.3.3] breaks serial i/o?
Date: Fri, 19 Oct 2001 12:12:00 -0000
Message-id: <20011019141204.L1140@saturn.billgatliff.com>
References: <20011018161003.A3059@saturn.billgatliff.com> <20011018222406.C11830@redhat.com> <20011019085618.A5013@saturn.billgatliff.com> <20011019114712.A23101@visi.com> <20011019130301.A26885@redhat.com> <20011019133042.J1140@saturn.billgatliff.com>
X-SW-Source: 2001-10/msg00201.html

Guys:


Here's some of the (apparently) relevant code in gdb's RDI support:



gdb-5.0/gdb/rdi-share/serdrv.c

static int SerialOpen(const char *name, const char *arg)
{
...
 
#ifdef COMPILING_ON_WINDOWS
    {
        int port = IsValidDevice(name);
        if (OpenSerial(port, FALSE) != COM_OK)
            return -1;
    }
#else
    if (Unix_OpenSerial(port_name) < 0)
      return -1;
#endif
...


Since I'm not a Win32 programmer, I don't really know the semantics of
the OpenSerial call.  Does anyone know how to set the flow control
strategy?


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com