From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31748 invoked by alias); 1 Oct 2003 05:58:08 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 31740 invoked from network); 1 Oct 2003 05:58:06 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 1 Oct 2003 05:58:06 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 30E28D2DAF; Tue, 30 Sep 2003 22:58:06 -0700 (PDT) Date: Wed, 01 Oct 2003 05:58:00 -0000 From: Joel Brobecker To: gdb@sources.redhat.com Subject: Re: Using gdb with Borland's free compiler? Message-ID: <20031001055806.GB933@gnat.com> References: <200309282250.h8SMorcf026975@duracef.shout.net> <3F783251.2030009@redhat.com> <20031001000752.GA6807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031001000752.GA6807@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-10/txt/msg00008.txt.bz2 > So far the basic problem with just using cygwin's gdb seems to be lack > of understanding of MS-DOS paths. It should be doable to fix up gdb to > understand those better in the cygwin port, if that was the only > problem. This part is actually (almost) easy. By simply defining a few macros that do the conversion between DOS and cygwin formats, we managed to get a cygwin GDB that talks DOS paths. We never submitted these patches for approval because we felt they would never be accepted. After all, when you use a cygwin debugger, chances are you prefer to see cygwin paths. Maybe we could compromise by using a two-state variable or a boolean variable. We would have cygwin paths by default, but changing the setting of this variable would allow you to get DOS paths instead? I say it's almost easy because we tested these changes against GNAT, which is a migw compiler. We never stress-tested it against a cygwin compiler for instance. The real annoying problem that we have been facing with a cygwin GDB is its dependence on the cygwin dll. That makes distribution of GDB binaries more challenging, because now we need to distribute this DLL too. All is fine when the customer host doesn't use cygwin, but it becomes potentially problematic when he does and the DLL versions don't match... ACT's two cents... -- Joel