Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Mon, 22 Feb 1999 17:12:46 -0500 Message-Id: <199902222212.RAA01050@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: curtis AT pdi DOT com CC: cygwin AT sourceware DOT cygnus DOT com In-reply-to: <36D1D392.2FA663A3@pdi.com> (message from Curtis Galloway on Mon, 22 Feb 1999 14:00:50 -0800) Subject: Re: Debugging the cygwin DLL References: <36D1D392 DOT 2FA663A3 AT pdi DOT com> > Anyone have any hints for debugging the Cygwin dll? The messages I > found in the archive on the subject were pretty dated. You should be able to just use gdb to debug it, even as a dll. Have you tried? Hmmm, maybe it's one of those things that didn't make it into the last beta, or maybe it doesn't work as well as I think it does. If you did try, what happened? > Creating a static version of libcygwin.a seems to be the way to go. > If anyone has done this already in b20.1, I'd love to hear from > them. It can be done, but it's not that easy. The big problem is that the DLL has some initialization stuff that doesn't happen if you link it statically, and it expects some things to be in the dll vs the exe, like malloc, so you have to replace those as well. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com