From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin GCC and debug info source file paths
Date: Tue, 14 Aug 2012 20:50:00 -0000 [thread overview]
Message-ID: <502AB8D9.5050202@cygwin.com> (raw)
In-Reply-To: <k0e4g9$uuk$1@dough.gmane.org>
On 8/14/2012 2:13 PM, David Lindström 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 need to ask the folks at gnuarm.com to make mingw versions of GCC
available or use the debugging tools they provide.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
next prev parent reply other threads:[~2012-08-14 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 20:45 David Lindström
2012-08-14 20:50 ` Larry Hall (Cygwin) [this message]
2012-08-15 0:34 ` Ian Lance Taylor
2012-08-15 8:54 ` David Lindström
2012-08-16 0:44 ` David Lindström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502AB8D9.5050202@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).