From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20848 invoked by alias); 9 Aug 2006 17:40:57 -0000 Received: (qmail 20839 invoked by uid 22791); 9 Aug 2006 17:40:55 -0000 X-Spam-Check-By: sourceware.org Received: from heller.inter.net.il (HELO heller.inter.net.il) (192.114.186.73) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Aug 2006 17:40:52 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-248-25.inter.net.il [83.130.248.25]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id AER95938 (AUTH halo1); Wed, 9 Aug 2006 20:40:47 +0300 (IDT) Date: Wed, 09 Aug 2006 17:40:00 -0000 Message-Id: From: Eli Zaretskii To: Nikolay.Molchanov@Sun.COM CC: gdb@sourceware.org In-reply-to: <44D98D66.9060202@sun.com> (message from Nikolay Molchanov on Wed, 09 Aug 2006 00:23:18 -0700) Subject: Re: Why gdb 6.5 prints fullname in /cygdrive/... format om Windows? Reply-to: Eli Zaretskii References: <44D832EE.2040405@sun.com> <44D8E404.5050407@Sun.COM> <44D98D66.9060202@sun.com> 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/msg00073.txt.bz2 > Date: Wed, 09 Aug 2006 00:23:18 -0700 > From: Nikolay Molchanov > Cc: gdb@sourceware.org > > >One way that should work is "strings -a foo.exe". You should see the > >name of each of your source files (either with or without a leading > >directory) and right after each file name the directory which was the > >current when you compiled that file. Please show both the file names > >and the directories that follow them. > > > > > Yes, it prints the directory with /cygdrive/: > > bash-3.1$ strings -a t1-g.exe | grep t1 > t1.c > /cygdrive/c/users/nik/t1/ If so, there's nothing GDB can do about that: it simply outputs the source file names as they are recorded in the debug info. > >In general, if you want to avoid such problems, you should be using a > >coherent set of tools. Which in practice means that a Cygwin build > >of GDB should be used with Cygwin front ends and other programs. If > >your front end cannot be built with Cygwin, you might consider using > >the MinGW GCC and GDB instead, which are native Windows executables > >and understand Windows-style d:/foo file names. > > > > > Yes, we will try to support these compilers as well in future, but our > primary > target is to provide a free open source IDE for java and C/C++ developers, > and this IDE shall work with Cygwin compilers on Windows The problem is, it's generally not feasible to have Cygwin and non-Cygwin executables work seamlessly together, and similarly for MSYS with non-MSYS executables (and UWIN as well, I think). More generally, any toolkit that modifies too much the basic OS interface in order to support Posix features beyond what's available on the Windows APIs, will always hit this problem sooner or later. In other words, I think the requirement to support all these compilers in the same build of the IDE is simply infeasible. You will probably be better off if you arrange for your IDE to build as Cygwin and MinGW applications, and provide both binaries for download. Then people could choose the proper binary according to the development tools they use. I don;t think there's a reason to believe that someone would need to mix development tools of different types in the same project. > So, if it is possible to provide an option to print fullname in > Windows format, we will very much appreciate it. That would mean to add code to the native MinGW port that would understand the Cygwin /cygdrive/ feature. Such a code will need to change each time Cygwin changes anything substantial in how this feature works. I think such coupling between two unrelated projects is not a good idea.