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
Message-ID: <36D1E0A5.D4B841D2@pdi.com>
Date: Mon, 22 Feb 1999 14:56:37 -0800
From: Curtis Galloway <curtis AT pdi DOT com>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: DJ Delorie <dj AT delorie DOT com>
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Debugging the cygwin DLL
References: <36D1D392 DOT 2FA663A3 AT pdi DOT com> <199902222212 DOT RAA01050 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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 AT sourceware DOT cygnus DOT com