Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Server-Uuid: 2d3b7162-db1d-11d3-b8ee-0008c7dfb6f1 Message-ID: <718198F862F1D411B10F0002A50A4DB1059FE8E1@e90wwce3.dx.deere.com> From: "Polley Christopher W" To: "'cygwin AT cygwin DOT com '" Subject: RE: Debugging cygwin Date: Tue, 26 Mar 2002 21:35:33 -0600 MIME-Version: 1.0 X-WSS-ID: 10BFE1811617747-01-02 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Bill, The debug_printf statements get printed when you run your program under strace. (see http://cygwin.com/faq/faq.html#TOC111 ) Also, here are some excellent tips that cgf has given on strace and debugging cygwin1.dll: http://www.cygwin.com/ml/cygwin/2000-11/msg01469.html (BTW, "google is your friend" http://www.google.com/search?q=debugging+cygwin1%2Edll ) HTH, Chris -----Original Message----- From: William Hubbard 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/