This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin GCC and debug info source file paths
- From: Ian Lance Taylor <iant at google dot com>
- To: David Lindström <info at davidlindstrom dot se>
- Cc: gcc-help at gcc dot gnu dot org, cygwin at cygwin dot com
- Date: Tue, 14 Aug 2012 15:55:28 -0700
- Subject: Re: Cygwin GCC and debug info source file paths
- References: <k0e4g9$uuk$1@dough.gmane.org>
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