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
Message-Id: <5.1.0.14.0.20020326190437.022f95d8@postoffice>
X-Sender: bill AT postoffice
Date: Tue, 26 Mar 2002 19:11:56 -0800
To: cygwin AT cygwin DOT com
From: William Hubbard <bill AT virtio DOT com>
Subject: Debugging cygwin
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Can someone point me to a how-to, or provide the steps, for getting set up 
so that I can debug cygwin1.dll?  I want to instrument the com routines to 
help zero in on a problem I am having with connecting gdb to a simulation 
environment via a virtual serial port (to determine if it is cygwin or the 
virtual serial port driver that is the problem).

I notice there are debug_printf statements in the code, already, but am 
clueless as to where this information gets printed.  If I at least knew 
that, I could add my own tracers, but I'd like to be able to step through 
the code as well.  I finally got cygwin1.dll to compile...so what's my next 
step?

Thanks,
Bill


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/