From mboxrd@z Thu Jan  1 00:00:00 1970
From: Curtis Galloway <curtis@pdi.com>
To: DJ Delorie <dj@delorie.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Debugging the cygwin DLL
Date: Sun, 28 Feb 1999 23:02:00 -0000
Message-ID: <36D1E0A5.D4B841D2@pdi.com>
References: <36D1D392.2FA663A3@pdi.com> <199902222212.RAA01050@envy.delorie.com>
X-SW-Source: 1999-02n/msg00726.html
Message-ID: <19990228230200.yDFrUpbGotsbucxmLZR5m6F36exl3WfYxi3NFnigMuw@z>

DJ Delorie wrote:
> 
> > 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?

Ah, indeed, if I

   gdb cygwin1.dll

and then

   gdb> exec-file myprogram.exe

I can debug functions within the cygwin DLL.  Very nice.

Unfortunately, gdb's use of signals seems to interfere with debugging the
cygwin signal handling code.  I think I'm stuck with using strace after all.

Thanks,
--Curtis

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com