This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: .debug_loc
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Keith Walker <keith dot walker at arm dot com>
- Cc: Michal Ludvig <mludvig at suse dot cz>, "" <gcc at sources dot redhat dot com>
- Date: Fri, 31 Jan 2003 12:53:16 -0500 (EST)
- Subject: Re: .debug_loc
- References: <4.3.2.7.2.20030131165828.0399eb58@mhsun1.maidenhead.arm.com>
On Fri, 31 Jan 2003, Keith Walker wrote:
> Michal,
>
> At 17:52 31/01/2003 +0100, Michal Ludvig wrote:
> >Hi Daniel,
> >I have a question on parsing .debug_loc on x86-64. Let's have this one:
> >
> > .section .debug_loc,"",@progbits
> >.LLST0:
> > .quad .LVL3-.text # Location list begin address (*.LLST0)
> > .quad .LVL5-.text # Location list end address (*.LLST0)
> > .value 0x1 # Location expression size
> > .byte 0x53 # DW_OP_reg3
> > [...]
> > .quad .LVL16-.text # Location list begin address (*.LLST0)
> > .quad .Letext0-.text # Location list end address (*.LLST0)
> > .value 0x1 # Location expression size
> > .byte 0x53 # DW_OP_reg3
> > .long 0x0 # Location list terminator begin (*.LLST0)
> > .long 0x0 # Location list terminator end (*.LLST0)
>
> These last 2 entries should be .quad in this case (as the DWARF3
> specification states:
>
> "The end of a given location list is marked by an
> end of list entry, which consists of a 0 for the
> beginning address and a 0 for the ending address."
>
> This looks like a compiler defect not correctly catering for the 64-bit
> addresses in the terminating entry.
Yeah, my bad.
I'll fix it.