bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/2582] New: dwarf2dbg.c embeds absolute filename path with hard-


From: burgess at impulse dot net
Subject: [Bug gas/2582] New: dwarf2dbg.c embeds absolute filename path with hard-coded / separator
Date: 18 Apr 2006 01:30:45 -0000

dwarf2dbg.c -- line 1476 of CVS version 1.81:

p[len] = '/';

This inserts a filesystem separator character when tacking the source filename 
back onto the source 
directory when providing the source-file's path for DWARF2 debugging 
information.  HOWEVER in 
Windows systems where the filename has been specified in Windows format, i.e. 
C:\Workspaces\Eclipse
\Blinky\init.s, this creates a filename in the DWARF2 debugging information 
that looks like C:
\Workspaces\Eclipse\Blinky/init.s -- and boy does that confuse ARM's Realview 
debugger for my ARM-
based embedded system.

You may ask why I'm doing this ... a fair question ... I am tied to the 
Realview debugger because of my 
particular JTAG interface, but the Realview debugger does not understand the 
default CYGWIN 
embedded pathnames of /cygdrive/c/workspaces/eclipse/blinky/*.  It wants 
Windows-format 
pathnames to be able to find the source files corresponding to the executable.  
By specifying the 
absolute Windows pathname in the call to as and gcc, this is accomplished OK!  
Or at least it was for 
gcc.

Sorry if I'm not filling in the bugzilla fields correctly, I'm new to this.

-- 
           Summary: dwarf2dbg.c embeds absolute filename path with hard-
                    coded / separator
           Product: binutils
           Version: 2.18 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gas
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: burgess at impulse dot net
                CC: bug-binutils at gnu dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=2582

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]