X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: =?iso-8859-1?Q?David_Lindstr=F6m?= Subject: Cygwin GCC and debug info source file paths Date: Tue, 14 Aug 2012 20:13:30 +0200 Lines: 16 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit Cc: gcc-help AT gcc DOT gnu DOT org X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. Mvh David Lindström -- 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