From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19537 invoked by alias); 9 Aug 2006 18:18:28 -0000 Received: (qmail 19529 invoked by uid 22791); 9 Aug 2006 18:18:28 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Aug 2006 18:18:24 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 0912648CDE0; Wed, 9 Aug 2006 14:18:22 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20677-01-2; Wed, 9 Aug 2006 14:18:21 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id 832CD48CBB2; Wed, 9 Aug 2006 14:18:21 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id E05BD47EFA; Wed, 9 Aug 2006 11:18:19 -0700 (PDT) Date: Wed, 09 Aug 2006 18:18:00 -0000 From: Joel Brobecker To: Bob Rossi Cc: Andrew STUBBS , gdb@sourceware.org Subject: Re: Why gdb 6.5 prints fullname in /cygdrive/... format om Windows? Message-ID: <20060809181819.GQ1385@adacore.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060809181020.GA23962@brasko.net> User-Agent: Mutt/1.4i 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/msg00076.txt.bz2 > 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. -- Joel