From: Jim Blandy <jimb@redhat.com>
To: Daniel Berlin <dan@dberlin.org>
Cc: gdb@sources.redhat.com
Subject: Re: Getting rid of the symbol_ranges and aliases stuff
Date: Fri, 05 Apr 2002 20:50:00 -0000 [thread overview]
Message-ID: <np1ydt77ne.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203251756520.6636-100000@dberlin.org>
Daniel Berlin <dan@dberlin.org> writes:
> This is the live range splitting extensions to stabs stuff. It works by
> having multiple symbols that are aliases to a given symbol at a given PC.
> In effect, it uses multiple symbols to simulate DWARF2 location lists.
> It could be reimplemented in terms of location functions, cleanly.
>
> But since nothing publicly available generates the info, I can't do that
> as part of a LOC_COMPUTED and LOC_COMPUTED_ARG implementation.
> Nor do I think I should be required to.
You should just ignore the old LRS stuff. The Dwarf 2 location lists
should be single symbols with the LOC_COMPUTED address class with a
`read_variable' method which use the PC from the frame it recieves to
choose the right location expression.
I guess I don't see how the old LRS stuff is in your way.
next prev parent reply other threads:[~2002-04-06 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 15:06 Daniel Berlin
2002-04-05 20:50 ` Jim Blandy [this message]
2002-04-05 21:31 ` Daniel Berlin
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=np1ydt77ne.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=dan@dberlin.org \
--cc=gdb@sources.redhat.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