MIME-Version: 1.0
In-Reply-To: <k0e4g9$uuk$1@dough.gmane.org>
References: <k0e4g9$uuk$1@dough.gmane.org>
Date: Tue, 14 Aug 2012 15:55:28 -0700
Message-ID: <CAKOQZ8wXhCTrMkm6yEBW1eysQO5jhaD+3x6AzHN=hTeBCSLueQ@mail.gmail.com>
Subject: Re: Cygwin GCC and debug info source file paths
From: Ian Lance Taylor <iant@google.com>
To: =?ISO-8859-1?Q?David_Lindstr=F6m?= <info@davidlindstrom.se>
Cc: gcc-help@gcc.gnu.org, cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Tue, Aug 14, 2012 at 11:13 AM, David Lindström
<info@davidlindstrom.se> wrote:
> Hi, I didn't know where to put this. I'm trying to use a cygwin build of GCC
> for arm (binaries from gnuarm.com). When I build a simple dummy application
> just doing some matrix multiplications in a loop, it creates a nice
> executable file with debug info, but the path to the source file is a cygwin
> path which is incompatible with the debugging tool I'm trying to use. I'm
> wondering if there's a way to generate the exe with relative paths to the
> source files, alternatively to use windows paths?
>
> The tool is Trace32 from Lauterbach, currently experementing with the arm
> simulator from the website.

You may be able to use GCC's -fdebug-prefix-map option.

Ian

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple