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: DJ Delorie <dj@delorie.com>
- Subject: Re: Debugging the cygwin DLL
- From: Curtis Galloway <curtis@pdi.com>
- Date: Mon, 22 Feb 1999 14:56:37 -0800
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- References: <36D1D392.2FA663A3@pdi.com> <199902222212.RAA01050@envy.delorie.com>
- Sender: cygwin-owner@sourceware.cygnus.com
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