Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 24 Apr 2003 21:33:26 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Debug tool Message-ID: <20030425013326.GA31825@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <8C6B052884783549B5D30C166853A514028C8372@usilms21.ca.com> <011c01c30aa5$0b599e10$14f286d9@ellixia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Apr 24, 2003 at 03:28:33PM -0700, Andrew DeFaria wrote: >Elfyn McBratney wrote: > >>>Please let me know a good debug tool to debug (step into) cygwin compiled >>> >>> >>code). >> >>gdb >> >Or for a graphical interface try insight (Note: gdb used to do this but >sometime around 1.1.3-20 or so it changed). And 1.1.3-20 would be what again? It doesn't resemble any version number for cygwin or gdb. The insight/gdb separation was announced here: http://sources.redhat.com/ml/cygwin-announce/2002-12/msg00014.html It's hardly new at this point. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/