From: Daniel Jacobowitz <drow@mvista.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Daniel Berlin <dberlin@dberlin.org>,
Michal Ludvig <mludvig@suse.cz>, gdb <gdb@sources.redhat.com>,
gcc@gcc.gnu.org
Subject: Re: Reference to .debug_loc
Date: Fri, 14 Feb 2003 20:40:00 -0000 [thread overview]
Message-ID: <20030214204041.GA15348@nevyn.them.org> (raw)
In-Reply-To: <20030214213521.J1717@sunsite.ms.mff.cuni.cz>
On Fri, Feb 14, 2003 at 09:35:21PM +0100, Jakub Jelinek wrote:
> On Fri, Feb 14, 2003 at 02:51:24PM -0500, Daniel Jacobowitz wrote:
> > > >>Or is there another way?
> > > >
> > > >At a guess it should be like DW_AT_ranges:
> > > > .long .Ldebug_ranges0+0x0 # DW_AT_ranges
> > > >
> > > >I.E. dw2_asm_output_offset, rather than dw2_asm_output_delta, in GCC.
> > > >
> > >
> > > It's supposed to be the offset from the beginning of the debug_loc
> > > section.
> > > Will this do that?
> >
> > I think so. The result will be something like .Ldebug_ranges0 +
> > (.LLST0-.Ldebug_loc0). If the assembler won't take that then we'll
> > have to track addresses for loclists the same as we do for rangelists.
>
> Why simple .long .LLST0 is not sufficient (@secrel(.LLST0) on IA-64)?
> It is not the only place where gcc relies on VMA of debugging sections
> to be 0 if the architecture lacks section relative relocations.
I suppose that would work. Do you know why DW_AT_ranges is done the
way it is?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-14 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 14:57 Michal Ludvig
2003-02-14 15:26 ` Daniel Jacobowitz
2003-02-14 19:24 ` Daniel Berlin
2003-02-14 19:51 ` Daniel Jacobowitz
2003-02-14 20:23 ` Daniel Berlin
2003-02-14 20:35 ` Jakub Jelinek
2003-02-14 20:40 ` Daniel Jacobowitz [this message]
2003-02-17 14:55 ` Michal Ludvig
2003-02-14 21:09 ` Daniel Berlin
2003-02-19 10:51 ` Michal Ludvig
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=20030214204041.GA15348@nevyn.them.org \
--to=drow@mvista.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jakub@redhat.com \
--cc=mludvig@suse.cz \
/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