From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22303 invoked by alias); 9 Aug 2006 18:23:55 -0000 Received: (qmail 22294 invoked by uid 22791); 9 Aug 2006 18:23:55 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao05.cox.net (HELO eastrmmtao05.cox.net) (68.230.240.34) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Aug 2006 18:23:53 +0000 Received: from localhost.localdomain ([70.181.32.198]) by eastrmmtao05.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060809182349.LLHT7951.eastrmmtao05.cox.net@localhost.localdomain>; Wed, 9 Aug 2006 14:23:49 -0400 Received: from bob by localhost.localdomain with local (Exim 4.60) (envelope-from ) id 1GAsin-00046S-Ba; Wed, 09 Aug 2006 14:24:01 -0400 Date: Wed, 09 Aug 2006 18:23:00 -0000 From: Bob Rossi To: Joel Brobecker Cc: Andrew STUBBS , gdb@sourceware.org Subject: Re: Why gdb 6.5 prints fullname in /cygdrive/... format om Windows? Message-ID: <20060809182401.GD23962@brasko.net> References: <44D832EE.2040405@sun.com> <17624.26822.63634.129976@kahikatea.snap.net.nz> <20060808131823.GB16362@nevyn.them.org> <20060808152923.GA23703@trixie.casa.cgf.cx> <20060808173127.GA27456@brasko.net> <20060808173555.GA24654@nevyn.them.org> <44D9A819.1010007@st.com> <20060809181020.GA23962@brasko.net> <20060809181819.GQ1385@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060809181819.GQ1385@adacore.com> User-Agent: Mutt/1.5.11 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00077.txt.bz2 On Wed, Aug 09, 2006 at 11:18:19AM -0700, Joel Brobecker wrote: > > Of course, don't count on this working. The GDB could easily be built > > on Cygwin, and the cygwin1.dll delivered. In this case there will be > > no cygpath, and your front end won't work. > > Just FYI, and Chris might contradict me, but delivering cygwin1.dll > introduces some issues that are not necessarily easy to overcome. > One of them is compatibility when the end user already has a cygwin > installation present on his system. When that happens, very often > the two will not be able to coexist at the same time and the user > may see error messages saying that the application could not be > loaded because of such issues. We've been able to work around this > problem so far by having the cygwin install and our debugger use > the same one (which one do you choose?), but I think it might be > a risky practice. Yes, this is very familiar to me. http://sourceware.org/ml/cygwin/2005-03/msg00700.html I followed the second solution and it worked fine. Bob Rossi