This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Debugging the cygwin DLL
- To: curtis@pdi.com
- Subject: Re: Debugging the cygwin DLL
- From: DJ Delorie <dj@delorie.com>
- Date: Mon, 22 Feb 1999 17:12:46 -0500
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-reply-to: <36D1D392.2FA663A3@pdi.com> (message from Curtis Galloway on Mon,22 Feb 1999 14:00:50 -0800)
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- References: <36D1D392.2FA663A3@pdi.com>
- Sender: cygwin-owner@sourceware.cygnus.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@sourceware.cygnus.com