From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25726 invoked by alias); 8 Aug 2006 21:31:37 -0000 Received: (qmail 25711 invoked by uid 22791); 8 Aug 2006 21:31:36 -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; Tue, 08 Aug 2006 21:31:31 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-44-109.inter.net.il [80.230.44.109]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id AEO76775 (AUTH halo1); Wed, 9 Aug 2006 00:31:24 +0300 (IDT) Date: Tue, 08 Aug 2006 21:31:00 -0000 Message-Id: From: Eli Zaretskii To: Nikolay Molchanov CC: gdb@sourceware.org In-reply-to: <44D8E404.5050407@Sun.COM> (message from Nikolay Molchanov on Tue, 08 Aug 2006 12:20:36 -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> 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/msg00061.txt.bz2 > Date: Tue, 08 Aug 2006 12:20:36 -0700 > From: Nikolay Molchanov > Cc: gdb@sourceware.org > > Eli, the executable is built by Cygwin gcc,, but I don't know how to > find out the file name and the compilation directory actually recorded > in the debug info of the executable. Which command prints this info? 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. > And the main problem with file names in Cygwin format is that Java > does not understand such names, so we have to translate them to > Windows format, which is not a trivial task in general case, because > there could be many mounted filesystems, like "/tmp/...", > "/usr/include/..." > and so on. 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.