Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 21 Jan 2004 13:37:10 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: snapshot now == 1.5.7 soon, please try
Message-ID: <20040121183710.GA25477@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20040120230704 DOT GA15076 AT redhat DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0401211010340 DOT 17483 AT eos> <20040121170832 DOT GA17823 AT redhat DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0401211109570 DOT 17483 AT eos> <20040121182042 DOT GA25111 AT redhat DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0401211223310 DOT 17483 AT eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0401211223310.17483@eos>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

On Wed, Jan 21, 2004 at 12:27:52PM -0600, Brian Ford wrote:
>On Wed, 21 Jan 2004, Christopher Faylor wrote:
>
>> Ok.  So, I took ten minutes and debugged the problem myself and I'll
>> check in a fix.
>>
>Thank you.
>
>That is why I asked.  You know your way around, so it takes you *much*
>less time.

This was only a little knowing my way around.  It was really pretty
basic debugging.

The code was hanging in read.  So, I set a breakpoint in readv, which,
on code inspection, is what read calls.  Single stepping along, I came
to the function that was hanging.  Tracing that along I came to the
Windows API function that was hanging.  Realizing that this function
obviously wasn't supposed to be hanging, I theorized that the com port
wasn't being opened properly.  So, I set a breakpoint on
fhandler_serial::open and notice nothing special there.  Then I noticed
that fhandler_serial::open calls fhandler_base::open.  I noticed that
fhandler_base::open has special serial considerations.  Stepping over
those, I saw they weren't being exercised.  So I fixed that using the
same technique you used here:

2003-11-12  Brian Ford  <ford AT vss DOT fsi DOT com>

        * dtable.cc (build_fh_pc): Use DEV_SERIAL_MAJOR to catch all serial
        ports.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/