Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 26 May 2000 17:32:15 -0400 To: cygwin users Subject: Re: Troubles with gdbtk Message-ID: <20000526173215.B23535@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin users References: <20000526170354.14156.qmail@web109.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000526170354.14156.qmail@web109.yahoomail.com>; from earnie_boyd@yahoo.com on Fri, May 26, 2000 at 10:03:54AM -0700 On Fri, May 26, 2000 at 10:03:54AM -0700, Earnie Boyd wrote: >Thanks for replying Scott. You've described the same problems I'm having. If >you use the non-GUI (i.e. the -nw switch), the source code is displayed >properly. This is a feature of the pathing changes I described concerning \ vs >/. It has caused a bug in gdbtk when it passes the source file name to the tk >routines to display it. I haven't found where this happens in gdbtk source >yet, it's difficult to debug a debugger that's broken. The console version of gdb works fine. Just type: "gdb -nw whatever". cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com