Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A242AC7.2C9B0DFD@delcomsys.com> Date: Tue, 28 Nov 2000 16:59:35 -0500 From: Patrick Doyle X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en,zh,zh-CN,zh-TW MIME-Version: 1.0 To: cygwin Subject: Debugging cygwin1.dll Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I am certain I have seen this on the mailing list before, but I cannot seem to find it. Could somebody please summarize tips for debugging cygwin1.dll. I have several specific questions. If somebody would care to answer them, I would be very grateful. 1) Do all of the various _printf calls in the source (debug_printf(), syscall_printf, etc...) wend their way to strace, or do they go somewhere else? If they go somewhere else, how can I capture them? 2) If I wanted to step into cygwin calls with GDB, (how) can I do that? 3) I have successfully built cygwin1.dll from the CVS snapshot. If I want to try it, do I have to exit all of my cygwin apps, install it in /bin, and then restart my cygwin apps? Or can I run a specific cygwin app using my new DLL without going through all of this? If the answers to these questions are in the mailing list archive somewhere, please feel free to tell me, and I will go dig them out myself. Thanks for any pointers you can give me. --wpd -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com